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.
Im not aware of a way of updating every single API in the workspace with this im afraid - perhaps one of the other forum users can help.
If you do have the option of rolling back to a previous version - perhaps thats one of the easiest answers? Although please check the release notes and make sure whatever version you roll back to has latest versions of log4j files.
If you rolll back to a version with old log4j files you can just overwrite them yourself - cos you definitely want the latest files due to that log4j security issue that was found in late November/early December last year