New issue
Advanced search Search tips

Issue 769333 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

why chrome proxy addon change request

Reported by wangxi....@gmail.com, Sep 27 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. install any proxy addon like swithyomega
2. turn on the proxy
3. noticed the request received on server side has has a little bit different then the previous on (without proxy on)

What is the expected behavior?
request should be same when chrome proxy is on

What went wrong?
I am doing web develop and I use chrome proxy addons switchyomega to do quick proxy setting.

The proxy server I am using is based on node express, which is running on localhost 3000

I noticed that when I turn on proxy (which redirects my web page request to nodejs express which runs on localhost 3000 ), the request object received by express changed a little bit

e.g.

If I type http://localhost:3000 in address bar, without proxy addon turned on, in node express I get a request object with url property value "/" But when I turn on proxy(I do not by pass localhost), I get a request object with url property value "localhost:3000"

Any idea what is going on when the chrome proxy addon is on ? Thanks.

WebStore page: 

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
I tried directly setting proxy in the chrome -> setting, I also noticed the request got modified for that req.url properties. 


Labels: Needs-Triage-M61
Cc: kkaluri@chromium.org
Labels: TE-NeedsTriageFromMTV
Unable to triage this issue from TE because of unavailability of proxy setup, hence adding TE-NeedsTriageFromMTV for further triage
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 4

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment