Modify Header Value (HTTP Headers)

Didn't work

does not work in brave linux at all, even the example

Doesn't work for POST request, but it says for all requests. Waste of time

It stopped working after the latest update

Not working properly for existing headers

Modify "Accept" header doesn't work. Settings: "*" "Accept" "application/json,text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8" It also doesn't print to console. Chrome 62.0

I was comparing this with Requestly and liked that it was free, but it doesn't seem to be completely compatible with HTTP/2 protocol. No JS/CSS resources would load from an IIS website I was working on and I kept seeing a "net::ERR_HTTP2_PROTOCOL_ERROR" logged. I disabled this extension and the issue was immediately resolved. I can't use this if it's going to randomly cause errors by preventing Chrome from consistently loading resources.

Seems to work only with GET requests. I lost several hours searching a bug, before I found out, that the header of POST requests are not modified by this plugin.

Doesn't work sometimes. At random intervals, this extension stops doing the one thing it's designed to do: inject headers in browser requests. There is really no consistency to this, I had to simply disable the extension and use another. Since this one has URL filtering(and the other one doesn't) I'm still leaving this as installed. Otherwise, there's no real reason for me to keep this. Consistency is vital.

lacks proper guidance on how to use it.

Just couldn't get it to work for me as I wanted & the ux not great :-(

No backup option...

This extension does appear to work as advertised but there's a lot of room for improvement in the GUI and instructions. For example, the instructions explain what each column does by assigning them a number and saying, "Column 1 does this, Column 2 does that," etc, but the columns in the actual GUI aren't numbered. They are NAMED. So when you read "Column 9 does so and so," you can't just look down and find "Column 9" because there is no such label. You have to sit there and count the columns up to 9 to see which one they are referencing. Another problem (which could be user error) is that the 'Sub' checkbox doesn't appear to work properly. The instructions state that if 'Sub' is NOT checked, "the header will be applied to the exact URL(s) matching the given URL." However, I have yet to find a configuration in which checking the 'Sub' box activates the rule. The rules only work when 'Sub' is unchecked. According to the instructions, if I leave it unchecked, the changes should only apply to the EXACT URL entered. To reproduce the problem, create a rule with the following values: URL: https://www.whatismybrowser.com/detect/what-http-headers-is-my-browser-sending Domain: <checked or unchecked> (value doesn't appear to matter) Sub: <checked> Header Name: User-Agent Add: <checked> Modify: <unchecked> Remove: <unchecked> Header Value: Test 123 State: ACTIVE Now browse to the URL listed in the rule and view the displayed "USER-AGENT" header value. Note that the User-Agent does NOT display "Test 123." Now go back to the rule and uncheck the "Sub" box and then reload the test page. Note that the User-Agent now displays "Test 123." Since I specified the EXACT URL and then visited that exact URL, I would expect the User-Agent to display "Test 123" both when 'Sub' is unchecked and when it is checked. This means I have yet to be able to create a rule that applies only to a specific URL and not the entire site.

Doesn't modify existing http header item.