New issue
Advanced search Search tips

Issue 810905 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 827582
Owner: ----
Closed: Dec 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Proj-Servicification

Blocking:
issue 721414



Sign in to add a comment

Support early response header modification with Network Service + WebRequest

Project Member Reported by roc...@chromium.org, Feb 9 2018

Issue description

The WebRequest API allows extensions to modify incoming response headers very early during response handling, such that e.g. an extension can modify Set-Cookie and this is specified to affect the cookie value stored before the response is dispatched through the rest of the stack.

There is currently no way to support this on top of the Network Service. It's unclear how important this API feature is, so one option may be to omit support altogether and break the API. More investigation needed.
 
Blocking: 721414

Comment 2 by j...@kialo.com, Feb 23 2018

In a similar vein, I would very much like to modify the *status line* (e.g. "HTTP/1.0 200 OK") of responses in the webRequest.onHeadersReceived callback. The numeric part of the status line ('200')  is already exposed as a 'header' with key name 'status' but editing the value has no effect. 

It's true that the status line is NOT a header, as per RFC2616 (and subsequent RFCs), but modifying the status code in an extension could be very useful, e.g. for QA personnel looking to simulate internal errors on the server to trigger behavior in the front-end.

Comment 3 by rockot@google.com, Feb 26 2018

This bug is for tracking work to port existing WebRequest API features to new networking architecture in Chrome.

I think it's unlikely that we'd implement the feature you're requesting in c#2, but if you would like to request it, you should file a Feature Request at https://crbug.com/new rather than posting a comment here.

Comment 4 by j...@kialo.com, Feb 26 2018

My thinking was that such a modification would require being done at a similar time and place as this bug; plus, as is so often the case with large, popular projects, creating new tickets is often an invitation to be told "that ticket already exists, stop wasting our time." So, this is a refreshing change, and I will do it.

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

this is for investigation only. Not blocking canary for now.

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

Labels: Hotlist-KnownIssue
Mergedinto: 827582
Status: Duplicate (was: Available)

Comment 8 Deleted

Sign in to add a comment