Modify Header Value (HTTP Headers)
Add, modify or remove a header for any request on desired domains.
Modify Header Value (HTTP Headers) is an extension that can add, modify or remove an HTTP-request-header for all requests on a desired website or URL. This Addon is very useful if you are an App developer, website designer, or if you want to test a particular header for a request on a website.
Key features:
1. Easily add, modify or remove a header for any request on desired domains.
2. For a complete list of HTTP headers, please take a look at the list of all HTTP Header Fields on the Wikipedia page (https://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
3. Clicking on the Toolbar icon opens a UI to quickly switch the Addon ON or OFF, or open the options page.
4. Each header item has several options to adjust (see add-on's Options page for details)
5. You can add several header items and active or inactive them separately.
6. An example in the options page shows a tutorial on "How to add a custom header".
Note: to report bugs, please visit addon's homepage (https://mybrowseraddon.com/modify-header-value.html) and fill out the bug report form.
Latest reviews
Doesn't work for POST request, but it says for all requests. Waste of time
Thanks you for this plugin: I added a custom authorization header in my browser to login without going to the login page to enter email and password
awesome plugin! thanks a lot!
Very useful extension. Note: I need to change the Host: header to test a cloudfront setup before going live. That did not work in chrome, but it works with this same extension on Firefox. I suspect Chrome changed a setting that prohibits messing with the Host header ?
Used this for debugging OAuth X-Forwarded headers on local setups and works great, very helpful, thanks!
Can double check again after chrome update? Seems to be broken with me.
the URL filter works well, and the UI is easy to understand
the URL filter works well, and the UI is easy to understand
Perfectly acceptable application for my use case, works even faster than Requestly from what I've noticed
Perfectly acceptable application for my use case, works even faster than Requestly from what I've noticed
Worked for me!
Worked for me!
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.
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.
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.
Fonctionne bien sur Firefox, mais ne marche pas sur Brave.
No backup option...
No backup option...
Everything worked fine, but now it stopped working correctly, sets the title only for the html page, other resources are now unchanged, which is extremely bad :c
Everything worked fine, but now it stopped working correctly, sets the title only for the html page, other resources are now unchanged, which is extremely bad :c
It stopped working after the latest update
It stopped working after the latest update
Useful specific domain selection
Useful specific domain selection
Ne fonctionne simplement pas totalement incapable de modifier un header de réponse
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.
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.
Not a very friendly UI yeah but it really does work, nice job!
Not a very friendly UI yeah but it really does work, nice job!
I just love it.
I just love it.
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.
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.
OMG THANK YOU THIS WORKS AMAZING. ITS SO EASY TO USE. ONCE YOU HAVE EVERYTHING SETUP ITS LITERALLY ONE CLICK!! :) 10/10
OMG THANK YOU THIS WORKS AMAZING. ITS SO EASY TO USE. ONCE YOU HAVE EVERYTHING SETUP ITS LITERALLY ONE CLICK!! :) 10/10
Not working properly for existing headers
Not working properly for existing headers
Worked well for me, and it allows me to control configuration by URL, it's very useful to me. Thanks!
Worked well for me, and it allows me to control configuration by URL, it's very useful to me. Thanks!
totally helps me. it didn't work when I upgraded my chrome to version 76, until reverted back to chrome 75
totally helps me. it didn't work when I upgraded my chrome to version 76, until reverted back to chrome 75
Worked well for what i wanted to use it for, simple and useful
Worked well for what i wanted to use it for, simple and useful
Doesn't modify existing http header item.
Doesn't modify existing http header item.
lacks proper guidance on how to use it.
lacks proper guidance on how to use it.
It works. Perfect tool for testing SSO configurations. The interface is a little weird but it works great. Time saver.
It works. Perfect tool for testing SSO configurations. The interface is a little weird but it works great. Time saver.
