This repository has been archived by the owner on May 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
should change method to GET when following 303 redirect #11214
Labels
Comments
XHR in Chrome, Safari, FF does change request method to GET on 303 redirects, as expected. |
@WojtekKruszewski Haha, I stumbled over this issue when Googling for redirect issues with PhantomJS, you are not alone! 👍 :) |
👍 |
jprince
pushed a commit
to jprince/sleepers-and-keepers
that referenced
this issue
Jul 14, 2015
This is a workaround needed to make the test for removing keepers (in league_manager_spec) pass. There's currently a bug in PhantomJS (ariya/phantomjs#11214) that causes PhantomJS to make a request for 303 redirect with the original request method, in this case DELETE instead of a GET.
👍 |
Yup I have the same when using poltergeist which is based on phantomjs. |
👍 |
Issue still exists! |
...and still exists |
and still still exists ... |
Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When my server responds to PUT/DELETE with 303 redirect, PhantomJS follows the redirect with original request method. It correctly changes request method to GET after POST requests. Here's a snippet from my server log:
RFC2616 states that:
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource.
http://tools.ietf.org/html/rfc2616#section-10.3.4
The text was updated successfully, but these errors were encountered: