Request Headers (including CORS) Modifier icon

Request Headers (including CORS) Modifier

by L.Vladikov Β· Developer Tools
Manifest V3 Free
View in Chrome Web Store Data as of 16 Oct 2026

Modifies request headers (including CORS) for development purposes!

Users
56
0 in 30 days
Rating
5.0 / 5
unchanged in 30 days
Ratings
1
0 in 30 days
Store rank
#104K
#87K among extensions
Version
2.3
updated 20 Jun 2025

Users

monthly, 16 months
13060Jun 2025Mar 2026Oct 2026
Latest, 16 Oct 2026: 56 usersMove the mouse over the chart for any month

Ratings count

monthly, 16 months
001Jun 2025Mar 2026Oct 2026
Latest, 16 Oct 2026: 1 ratingsMove the mouse over the chart for any month

The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.

About Request Headers (including CORS) Modifier

πŸ‘¨πŸ»β€πŸ’» This Extension is intended for developers and it modifies Request Headers, either through the extension’s main icon or via an exposed API. The API can be accessed from the console or sideloaded scripts (such as Tampermonkey), making it ideal for automated workflows. πŸ’» The API includes enable() and disable() methods for toggling header modifications directly from the global namespace. You can also add, remove and clear either hostnames or headers, and the passed data can be strings, arrays, objects (for the headers) or arrays of objects. Methods include addHostname, addHostnames, removeHostname, removeHostnames, clearHostnames, addHeader, addHeaders, removeHeader, removeHeaders, clearHeaders. All API methods return a Promise that resolves to a boolean indicating success (true) or failure (false). πŸ‘‰ API Usage: The extension exposes a global API object window.requestHeaderModifier that allows you to control its functionality programmatically from your browser's developer console, a website's script (if allowed by CSP), or user script managers like Tampermonkey. All API methods return a Promise that resolves to a boolean indicating success (true) or failure (false). πŸ“– enable window.requestHeaderModifier.enable(); // Enables the header modification functionality. This will apply the currently saved rules. Returns true on success πŸ“– disable window.requestHeaderModifier.disable(); // Disables the header modification functionality. This will clear all active rules. Returns true on success πŸ“– addHostname window.requestHeaderModifier.addHostname(hostname); // Adds a new hostname to the list of target hostnames. If the hostname already exists, no change is made. πŸ”€ Parameter: hostname (string): The hostname to add (e.g., "api.example.com"). ✍️ examples: await window.requestHeaderModifier.addHostname("newapi.domain.com"); // Adds "newapi.domain.com" await window.requestHeaderModifier.addHostname("api.another.net"); // Adds "api.another.net" πŸ“– addHostnames window.requestHeaderModifier.addHostnames(hostnames); // Adds multiple hostnames to the list of target hostnames. Duplicate hostnames will be ignored. πŸ”€ Parameter: hostnames (string[]): An array of hostnames to add (e.g., ["app.domain.com", "app.example.com"]). ✍️ example: await window.requestHeaderModifier.addHostnames([ "api.test.com", "localhost:3000", ]); // Returns true on success πŸ“– removeHostname window.requestHeaderModifier.removeHostname(hostname); // Removes a specific hostname from the list of target hostnames. πŸ”€ Parameter: hostname (string): The hostname to remove. ✍️ example: await window.requestHeaderModifier.removeHostname("newapi.domain.com"); // Removes "newapi.domain.com" πŸ“– removeHostnames window.requestHeaderModifier.removeHostnames(hostnames); // Removes multiple hostnames from the list of target hostnames. Hostnames not found will be ignored. πŸ”€ Parameter: hostnames (string[]): An array of hostnames to remove. ✍️ example: await window.requestHeaderModifier.removeHostnames([ "api.old.com", "dev.api.net", ]); // Returns true if any hostnames were removed, false otherwise πŸ“– clearHostnames window.requestHeaderModifier.clearHostnames(); // Clears all hostnames from the list, effectively disabling header modification for all domains until new hostnames are added. ✍️ example: await window.requestHeaderModifier.clearHostnames(); // Clears all hostnames πŸ“– addHeader window.requestHeaderModifier.addHeader(header); // Adds a new custom request header or updates an existing one if a header with the same name already exists. πŸ”€ Parameter: header (string | object): The header to add. String format: "Header-Name: Header-Value" (e.g., "X-Custom-Auth: mytoken123") Object format: { "headerName": "headerValue" } (e.g., { "X-Client-ID": "app-123" }) ✍️ examples: // Using string format await window.requestHeaderModifier.addHeader("X-My-Header: MyValue"); // Using object format await window.requestHeaderModifier.addHeader({ "Content-Type": "application/json", }); // Updating an existing header (will overwrite "MyValue" with "NewValue") await window.requestHeaderModifier.addHeader("X-My-Header: NewValue"); πŸ“– addHeaders window.requestHeaderModifier.addHeaders(headers); // Adds multiple request headers to the list. If headers with the same names exist, their values will be updated. πŸ”€ Parameter: headers ((string | object)[]): An array of headers to add. Each element can be a string like "Header-Name: Header-Value" or an object like { "headerName": "headerValue" }. ✍️ examples: // Using string format array await window.requestHeaderModifier.addHeaders([ "X-My-Header: Value1", "Y-My-Header: Value2", ]); // Returns true on success // Using object format array await window.requestHeaderModifier.addHeaders([ { "Content-Type": "application/json" }, { "Accept-Language": "en-US" }, ]); // Returns true on success // Mixing formats and updating existing await window.requestHeaderModifier.addHeaders([ "Cache-Control: no-cache", { "X-My-Header": "UpdatedValue" }, // This will update X-My-Header if it exists ]); // Returns true on success πŸ“– removeHeader window.requestHeaderModifier.removeHeader(header); // Removes a specific custom request header by its name. The value part of the input is ignored for removal. πŸ”€ Parameter: header (string | object): The header to remove. Only the header name is considered for removal. String format: "Header-Name: AnyValue" (e.g., "X-My-Header: ignored") Object format: { "headerName": "ignoredValue" } (e.g., { "Content-Type": "ignored" }) ✍️ examples: // Using string format await window.requestHeaderModifier.removeHeader("X-My-Header: something"); // Removes X-My-Header // Using object format await window.requestHeaderModifier.removeHeader({ "Content-Type": "whatever" }); // Removes Content-Type πŸ“– removeHeaders window.requestHeaderModifier.removeHeaders(headers); // Removes multiple request headers from the list. Only the header name is considered for removal. Headers n…

Growth

WindowUsersChangeRatingsRating
7 days+2+3.7%00.00
30 days0+0.0%00.00
6 months+13+30.2%00.00
1 year+39+229.4%00.00

Chrome Web Store search rankings

Where Request Headers (including CORS) Modifier appears when people search the store, with the 30 day change
Search phrasePosition30 days
exist#99βˆ’80

Version history

1 versions recorded
2.320 Jun 2025

Details

Category
Developer Tools
First seen
20 Jun 2025
Size
165 KB
Languages
en
Pricing
Free
Extension ID
fbgpcnabikdbchnhloamemjepdmcfdak

Permissions and risk

Low riskimpact 2, likelihood 1
Permissions
declarativeNetRequeststorageactiveTab
Site access
<all_urls>
Can read and change data on every website you visit.

Alternatives to Request Headers (including CORS) Modifier

Extensions that rank for the same store searches or share the Developer Tools category, ordered by users