906728 - Network Panel: Resending requests does not update certain headers

Status: RESOLVED DUPLICATE of bug 1270096

(DevTools :: Netmonitor, defect, P2)

Description

[Brian Grinstead [:bgrins]]

Trying to use the new ability to edit and resend a request in the devtools, specifically to add a Cookie header, but it doesn't seem to work.  Clicking on the logged request in the console doesn't show any cookies, and the response from the remote server indicates that the cookie header was not present.

Tried changing Accept-Encoding and that didn't seem to work either.  Although adding a new heading (X-New-Heading: yes) did work.

Reported by jonathan1 in #devtools.

Comment 1

[Brian Grinstead [:bgrins]]

Steps to reproduce:
* Open network panel, right click on a request -> "Resend"
* Modify the "Cookie" value in the textarea
* Add a custom header in the textarea, like "X-New-Heading: yes"
* Press "Send"

Expected that the Cookie header will be updated in the new request, and X-New-Heading will be set to "yes".  Instead only "X-New-Heading" is set to yes.

This also happens with Accept-Encoding, and possibly other default HTTP headers

Comment 2

[meanyack]

I'm having the same issue. 

Currently I'm testing secure communication between my server and client. However, I realized it's not sending the cookie I set. It just sends the cookie page already have not mine.

Any progress on this issue?

Comment 3

[Nikolay Ivanov]

I have and issue resending a request containing file upload.

The first request is containing this params :
-----------------------------23383268939591
Content-Disposition: form-data; name="fileIndex"

0
-----------------------------23383268939591
Content-Disposition: form-data; name="objectType"


-----------------------------23383268939591
Content-Disposition: form-data; name="form"

After resend without any change they look like this.
[object Object]

And on the server side there are not POST or FILES data.

Comment 4

[Jarda Snajdr [:jsnajdr]]

Fixed in bug 1270096.