Forum Discussion

gladiator's avatar
gladiator
New Contributor
11 years ago

Issue with ReadyAPI 1.4.0 onwards

Hi,

 

I am facing a weird issue in Ready API 1.4.0 onwards.

What happens is in a PUT request whatever parameter I pass, if it has '/' then it encodes the parameter value '%2F'.

So if my parameter is 'author/ccp-1566' then it goes like 'author%2Fccp-1566' or 'pub-date=05/02/12' interprets as 'pub-date=05%2F02%2F12'

I have tried with 'Pre-Encoded Endpoints' option, Transfer-Encoding header but there is no luck.

 

This is not happening in 'Ready API 1.1.0 version. But this version takes lot of memory compare to the newer version. Please help me with this issue.

 

Thanks in advance.

5 Replies

    • gladiator's avatar
      gladiator
      New Contributor
      11 years ago

      Hello Tanya,

       

      I have checked with the new version but this is not working. :(

      But I must admit that with the new version you have resolved quite a lot memory issue. But because of this issue I am not able to use the latest version.

       

      Please let me know if you require any other information.

       

      Thanks.

      • TanyaYatskovska's avatar
        TanyaYatskovska
        Icon for Alumni rankAlumni
        11 years ago

        Hi Gladiator,

         

        Our R&D team has been working on improving the performance issues in the latest product versions. I’m glad that this affects you.

        As for the encoding issue, you need to enable the Disables URL-Encoding of the parameter value option for all your parameters as it's shown here:
        http://readyapi.smartbear.com/structure/parameters/start

         

        Does it help?