ChromeRestClient
ChromeRestClient copied to clipboard
jarrodek
Follow Location Header Redirects
Originally reported on Google Code with ID 48
What steps will reproduce the problem?
1. Install App
2. Send Request to REST end point which returns a 303 along with a Location Header.
3. Notice that the Rest Client follows the HTTP redirect.
What is the expected output? What do you see instead?
Could an enhancement be made in the options dialog box to disable following redirects
specified in the Location header.
What version of the product are you using? On what operating system?
Latest version as of 2/14/2012
Reported by kevinrs on 2012-02-14 20:00:32
Was just about to log this very request. Looks like you beat me by 3 hours.
A suggestion for one additional thing, once the Follow Redirects has been turned off,
it would be nice to have a button on the response page that allows you to follow the
redirect after seeing the result.
Oh, and don't forget our friend response code 307.
Reported by [email protected] on 2012-02-14 23:06:20
Unfortunately webkit team still has not implemented "followRedirects" flag for XMLHttpRequest
object. Without this flag it is not possible to correctly display results.
Why? It will return status code from request after redirect. Application will not even
detect any redirection because there is no event fired when redirecting.
Until this flag is not implemented this feature will not be enabled.
Reported by jarrodek on 2012-02-15 18:01:32
-
Status changed:
WontFix
Two years later! :smile: Can we revisit this -- see if it's now possible? It would make a major (positive) impact in my workflow if ARC would simply stop on the first HTTP response.
Hmm. Actually the implementation is there. I don't have UI for that. I'll add it in v11.
You just gone and made my day. :+1: Happy to help test/debug when it's ready!
The problem is with additional stuff I have to do when adding anything to the request panel. This case is request settings. If I add this to the panel you'd expect to save this with the request data when saving the request. You also expect it to be restored when recalling the request. Then you'd expect it to be exported to a file and imported back as a setting of the request.
It's just takes a while to build this things since adding as simple option as that it requires several additional changes. Currently my list includes several other changes and when my list clears (I hope week is enough) I will review this issue again.