New issue
Advanced search Search tips

Issue 776312 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task
Proj-Servicification



Sign in to add a comment

Add response URL to ResourceResponseHead

Project Member Reported by dhausknecht@google.com, Oct 19 2017

Issue description

URLLoaderThrottle::WillProcessResponse expects the response URL as a GURL and a separate ResourceResponseHead with all other response related info.

For this and probably also other places it would be desirable to have the response URL as part of the ResourceResponseHead to allow taking respective actions based on this URL.
 

Comment 1 by mmenke@chromium.org, Oct 24 2017

Components: -Internals>Network Internals>Network>Service

Comment 2 by laforge@google.com, Nov 7 2017

Components: -Internals>Network>Service Internals>Services>Network
Apologies, applied the wrong component in bulk.

Comment 3 by dxie@chromium.org, May 17 2018

Owner: mmenke@chromium.org
Status: Assigned (was: Available)
mmenke@, is this for all path or with network service only.

Comment 4 by mmenke@chromium.org, May 17 2018

Owner: ----
Status: Available (was: Assigned)
I think we only use URLLoaderThrottles with the network service?  Not sure on this one - more a question of whether anything specific is blocking on this one.  Not really familiar with URLLoaderThrottles, or the consumers of it.
This is a suggested cleanup/refactor and it doesn't block network service's canary launch. Leaving it as a P3 Task seems reasonable.

Comment 6 by dxie@chromium.org, May 22 2018

Labels: Hotlist-KnownIssue

Sign in to add a comment