# Why does Network tab on Developer Tools not allow some headers?

**URL:** <https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234>\
**Category:** Developer Tools\
**Tags:** feedback, issue\
**Created:** [November 13, 2023, 11:10pm UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234 "2023-11-13T23:10:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wybqogzigoxruxdhnp](https://avatars.discourse-cdn.com/v4/letter/w/90db22/32.png) [@wybqogzigoxruxdhnp](https://discourse.mozilla.org/u/wybqogzigoxruxdhnp)\
**Post date:** [November 13, 2023, 11:10pm UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234/1 "2023-11-13T23:10:57Z")

</div>

Why can I only edit some headers on Network Tab on Dev tools?

 ![image](https://us1.discourse-cdn.com/flex001/uploads/mozilla/original/3X/d/4/d492a866affaf644ea96bb8f85d291e4c0dd1996.png)

For example I can edit or remove accept header but not Referer as it is grayed out. Why is that functionality nerfed? Isn’t Developer Tools mant for developers? If so what’s the point of limiting them? They could copy it as curl if they wanted, it’s just more annoying.

---

<div class="post-metadata">

**Author:** ![martijn](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@martijn](https://discourse.mozilla.org/u/martijn)\
**Post date:** [October 4, 2025, 6:10pm UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234/2 "2025-10-04T18:10:20Z")

</div>

Almost 2y and still no answer to this question

---

<div class="post-metadata">

**Author:** ![Nicolas\_Chevobbe](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/nicolas_chevobbe/32/28203_2.png) [@Nicolas\_Chevobbe](https://discourse.mozilla.org/u/Nicolas_Chevobbe)\
**Post date:** [October 20, 2025, 9:48am UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234/3 "2025-10-20T09:48:58Z")

</div>

Those are the forbidden request headers ( [Forbidden request header - Glossary | MDN](https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_request_header) )

At the moment, we’re using fetch to resend the request, so we would need something more custom to be able to set those headers.

We have a bug on file to look into this: [983451 - Allow to customize Referer header in Netmonitor](https://bugzilla.mozilla.org/show_bug.cgi?id=983451)  
And also [1780171 - Add a (collapsed) section for read-only Headers in Edit-And-Resend](https://bugzilla.mozilla.org/show_bug.cgi?id=1780171) to avoid cluttering the UI with these read-only headers

---

<div class="post-metadata">

**Author:** ![SR\_Blinds](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/sr_blinds/32/75520_2.png) [@SR\_Blinds](https://discourse.mozilla.org/u/SR_Blinds)\
**Post date:** [November 24, 2025, 7:37am UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234/4 "2025-11-24T07:37:55Z")

</div>

Hey there!

The simple reason some headers are out is because the **browser itself** protects them for **security and integrity**.

If Dev let you instantly change core headers, it could compromise browser security or lead to invalid HTTP requests.

**Quick Fix:** If you need to test with a custom , your best bet is to **Copy the request as URL** and edit it in your terminal, or use a third-party extension like **Mod Header**.

---

<div class="post-metadata">

**Author:** ![Khan](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/khan/32/75218_2.png) [@Khan](https://discourse.mozilla.org/u/Khan)\
**Post date:** [January 3, 2026, 9:40pm UTC](https://discourse.mozilla.org/t/why-does-network-tab-on-developer-tools-not-allow-some-headers/124234/5 "2026-01-03T21:40:01Z")

</div>

I ran into a similar issue when working with network requests in developer tools. Sometimes certain headers don’t appear due to browser security restrictions like CORS or the way some requests are handled internally.

One workaround I found useful is using external tools or browser extensions for monitoring requests that require full header visibility. Also, double-checking that your request isn’t blocked or altered by ad blockers or privacy settings helps.

For developers who also work with related tools, I’ve found that some AI-powered utilities and browser extensions can simplify debugging and inspecting headers, especially when testing APIs or automated scripts.
