New issue
Advanced search Search tips

Issue 742523 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome sends "chrome-proxy: frfr" header to third party webservers

Project Member Reported by mmenke@chromium.org, Jul 13 2017

Issue description

This isn't the end of the world, but it does seem weird that we're sending this header to third party servers, given that it's a magical header just for the data reduction proxy.
 

Comment 1 by bengr@chromium.org, Jul 13 2017

Hmm. We should be removing it before putting it on the wire. Do you have a netlog?

Comment 2 by mmenke@chromium.org, Jul 13 2017

Hrm...If it's removed after we log headers, but before we send it over the wire, it would still appear in the NetLog, despite not being sent.  I'll check if that's what was happening tomorrow.

Comment 3 by bengr@chromium.org, Jul 18 2017

Are we logging headers we aren't sending?

Comment 4 by mmenke@chromium.org, Jul 18 2017

Status: WontFix (was: Untriaged)
Going to close this - I can't remember where I saw this header, but it was in a NetLog of some sort.

Comment 5 by mmenke@chromium.org, Jul 18 2017

And it could well be that we log things before the DRP removes the header.

Sign in to add a comment