New issue
Advanced search Search tips

Issue 686913 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

307 Redirect Behavior when using the POST method resulting 405

Reported by palarind...@gmail.com, Jan 30 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
Intermittent

What is the expected behavior?

What went wrong?
We are using ajax POST calls in our source code. But from last few days, we can see the POST Calls are getting redirected to GET using 307 automatically. Now as the GET are restricted from the API, the Get call fails with 405 (Method not allowed). And this happening for few ajax calls not every one. If has became almost impossible for us to work on Chrome now. Appreciate some quick solution to the problem.

Did this work before? Yes prior 53

Does this work in other browsers? Yes

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

 
Components: Internals>Network Blink>Network

Comment 2 by ajha@chromium.org, Jan 31 2017

Labels: Needs-Milestone
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
palarindampal@,

Could you please provide us the clear steps/Jsfiddle/html file to triage the issue further.

Thanks in advance.

Comment 4 by mmenke@chromium.org, Jan 31 2017

Noet that Chrome 53 is an old version of Chrome, Chrome 55 is the current stable version and Chrome 56 will be released in the next couple weeks, I believe.  Do you see this problem on more recent versions of Chrome?

Could you also provide an about:net-internals log of this happening.  Instructions:  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Comment 5 by phistuck@gmail.com, Jan 31 2017

Just to verify - you use POST AJAX calls in your application. Up until this issue started happening, it was not returning 307.
Since this issue started happening, it started returning 307 and also POST was changed to a GET request to the URL to which 307 redirected.

If any of this is incorrect, please, clarify.
We have a test for redirects: https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/http/tests/fetch/script-tests/thorough/redirect.js?q=redirect.js+package:%5Echromium$&dr
According to the test Chrome doesn't change methods for 307.

Anyway, a reproducible example and/or a net-internals log would be appreciated.
Could you please check a newer version of the browser and provide the net-internals log as suggested in comment #4? This will greatly help us in moving forward with the issue. Thank you!
Status: Archived (was: Unconfirmed)
Network bug triager here.  Archiving due to inactivity.    palarindampal@ if you still have the issue, please open a new bug and provide the information requested above.

Sign in to add a comment