Forum Discussion

xikandar's avatar
xikandar
Occasional Contributor
7 years ago

How to pass application/x-www-form-urlencoded requst in ReadAPI having plus sign '+' in request body

REST request doesn’t work and 400 Bad request is received in response from server when following request is sent in body with Media Type x-www-form-urlencoded. However sometime this services works pr...
ContentType
Media-Type
Post request
URL encoding
  • PaulMS's avatar
    PaulMS
    7 years ago

    You could add refresh_token and token_type as query parameters.

    There is a similar example in Soap UI documentation using the Post QueryString check box.

     

    https://www.soapui.org/rest-testing/understanding-rest-parameters.html

    For such requests, you can include parameters of the QUERY type into the request body. To do this, simply select the Post QueryString check box.

    This will remove QUERY parameters from the URL and will add them to the request body. 

     

    You could also use groovy script to encode data directly in the body of the request.

     

    Wrap the request data or just the token like this

    ${= java.net.URLEncoder.encode('string', "UTF-8")}

     

     

    https://www.soapui.org/testing-dojo/best-practices/understanding-rest-headers-and-parameters.html

    Character Encoding
    Special characters are encoded in the URL, by a mechanism called “percent encoding”. In this mechanism any character can be replaced by the percent symbol, followed by a two-digit hexadecimal value of the encoded character. If special characters (such as the hash character) need to be sent as actual data, they must be encoded. All other characters can optionally be encoded.

PaulMS's avatar
PaulMS
Super Contributor

Is the plus sign encoded in the request Raw tab?

xikandar's avatar
xikandar
Occasional Contributor
7 years ago

NO, it is not being encoded that's what makes me worried. Even by passing the Media-type "application/x-www-form-urlencoded" still the request is being sent as it is by ReadAPI without encoding. See the attached image.

Is there any way to get it done ?

    • xikandar's avatar
      xikandar
      Occasional Contributor
      7 years ago

      PaulMS
      Attached is an image of fiddler showing raw request of Postman, it replaces the + sign with %2B as shown in Image.

      Request in ReadyAPI also works by manually replacing + with %2B but point is that in an automated execution cycle it is not possible to detect and manually replace + with %2B.

      Is it a bug in ReadyAPI ? ideally it should replace it just like Postman. Can this be reported for fix ? or any Groovy script to URLencode request before sending.

      • PaulMS's avatar
        PaulMS
        Super Contributor
        7 years ago

        You could add refresh_token and token_type as query parameters.

        There is a similar example in Soap UI documentation using the Post QueryString check box.

         

        https://www.soapui.org/rest-testing/understanding-rest-parameters.html

        For such requests, you can include parameters of the QUERY type into the request body. To do this, simply select the Post QueryString check box.

        This will remove QUERY parameters from the URL and will add them to the request body. 

         

        You could also use groovy script to encode data directly in the body of the request.

         

        Wrap the request data or just the token like this

        ${= java.net.URLEncoder.encode('string', "UTF-8")}

         

         

        https://www.soapui.org/testing-dojo/best-practices/understanding-rest-headers-and-parameters.html

        Character Encoding
        Special characters are encoded in the URL, by a mechanism called “percent encoding”. In this mechanism any character can be replaced by the percent symbol, followed by a two-digit hexadecimal value of the encoded character. If special characters (such as the hash character) need to be sent as actual data, they must be encoded. All other characters can optionally be encoded.