ContributionsMost RecentMost LikesSolutionsRe: ASCI encoding for mac address failing after 3.20.1 update Hey richie Thank you for the workaround, it did solve the issue !! Are you aware of any way to apply this over all the REST calls in a project? I have hundreds of calls imported automatically via swagger protocol, and I would need to go to each Request containing a mac in the URL and change its advanced settings, which is of course not practical. Otherwise, as you said it is indeed an issue introduced in the new update, I can consider downgrading my ReadyApi Fadi ASCI encoding for mac address failing after 3.20.1 update Since the new ReadyAPI 3.20.1 update, REST calls containing mac addresses in the URL are not working anymore. For example, The following mac 5C:35:3B:D7:10:38 in the URL is interpreted as admin/homegateways/5C%253A35%253A3B%253AD7%253A10%253A38 while it should be /admin/homegateways/5C%3A35%3A3B%3AD7%3A10%3A38/ according to ASCII encoding. In fact, there is an extra "%25" before each column "%3A" The test steps are old ones and used to work as they are part of regression tests we do. Every test step containing a mac address in the URL is now failing, so there is clearly an issue. Solved