New issue
Advanced search Search tips

Issue 923908 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 923622
Owner: ----
Closed: Today
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

GET requests have content-length header

Reported by shmullys...@gmail.com, Yesterday (36 hours ago)

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Sign in to website
For example - https://online.lloydsbank.co.uk/personal/logon/login.jsp
2. Check http headers that are sent in the request
3. Notice Content-Length and Content-Type

What is the expected behavior?
These headers are not to be used in GET requests

What went wrong?
It causes problems on middleware proxies, like Squid

Did this work before? Yes 71.0.3578.98

Chrome version: 72.0.3626.64  Channel: beta
OS Version: 10.0
Flash Version:
 

Comment 1 Deleted

Comment 2 by susan.boorgula@chromium.org, Yesterday (35 hours ago)

Labels: Needs-Bisect Needs-Triage-M72

Comment 3 by shmullys...@gmail.com, Yesterday (34 hours ago)

To add:- I see that Chrome now makes an initial POST request (Request 1) with the correct content, but then makes a GET request (Request 2) once again with the content.
request 1.jpg
80.1 KB View Download
request 2.jpg
86.2 KB View Download

Comment 4 by shmullys...@gmail.com, Yesterday (32 hours ago)

This is not a problem with the headers. Rather it is a problem that Chrome is sending content in a GET request type.
See https://stackoverflow.com/questions/978061/http-get-with-request-body

Comment 5 by swarnasree.mukkala@chromium.org, Today (20 hours ago)

Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Needs-Feedback
Tried testing the issue on reported chrome #72.0.3626.64 using Windows 10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to "amazon.in" and signed into the account.
3.Opened Devtools->Network tab.
4.Opened a request that has "Request Method" as GET.
5.Opened Headers and observed the "Content-Length" and "Content-Type".
6.Followed the above steps on chrome version #71.0.3578.98, the same behaviour is seen.
Note: "https://online.lloydsbank.co.uk/personal/logon/login.jsp", as the link is related to internet banking could not check the issue using this link, hence used "amazon.in" for testing.

Attached screenshots for reference.
@reporter: Could you please review the above steps followed and screenshots and let us know if anything is missed from our end. Requesting you to provide any other URL that reproduces the issue so that it would be really helpful in triaging the issue further.
Thanks.!
923908_M71.png
1.0 MB View Download
923908_M72.png
1.0 MB View Download

Comment 6 by shmullys...@gmail.com, Today (14 hours ago)

After investigating, the problem is related to  issue 923622 .
Project Member

Comment 7 by sheriffbot@chromium.org, Today (14 hours ago)

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by mef@google.com, Today (12 hours ago)

Mergedinto: 923622
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment