Forum Discussion

stallewar's avatar
stallewar
New Contributor
9 years ago

POST instead of GET after 302 redirrect

Win 8 ReadyAPI ver 1.9 same thing 1.8.5
It's not corret behaviour do POST req after 302 Status-Code.
I'm doing POST request to auth form. In this request 302 -redirrect presets, after should follow GET req.
But in RAPI 1.9 after 302 -redirrect POST req follows.
See screens:

 

Spoiler
Curl request - good
Spoiler
RAPI request NOT GOOD
Spoiler
RAPI request NOT GOOD

 

Accorrding to https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html - it's not correct behaviour All good in SoapUI 5.3 )

3 Replies

    • stallewar's avatar
      stallewar
      New Contributor
      9 years ago

      Sure, I can check this problem with nightly build R!API, and we will do so.
      But, looking to yours answer, i have a question to SmartBear sales or Head of QA R!API ! I'm buying PRO commercial license of R!API, not to test it, but to use it in my work! It is not opensource version for community testing.
      And i'm worried of installing R!API nightly builds on same PC with PRO license, due license manager issues - Is there any documentation, how to do it clearly?

      Me and my team are using smartbear products for nearly five years, however, to date, the quality of the product, makes us look for workaround ways the use and afraid of bugs.

      • PJat's avatar
        PJat
        Contributor
        9 years ago

        Hi Stallewar,

        I understand that it worked in previous version of Ready! API in a different way, but correct behavior is to keep the same HTTP method when redirect is with status code 302. Both the rfc and wikipedia (not a good source of truth but still) explain it very clearly that the request method should not be changed if it is redirect 302.

        https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

        https://en.wikipedia.org/wiki/HTTP_302

         

        So, it's rather result of fixing an existing bug in Ready! API.

        If possible, I would recommend to use rediret with status code 303, then Ready! API will redirect with GET.