[GH-ISSUE #274] Description for Content-Type and Authorization headers not disabled despite docs #73

New issue

Closed

opened 2026-03-16 12:24:22 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 12:24:22 +03:00

Owner

Originally created by @yousefmarey12 on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/hoppscotch/docs/issues/274

Originally assigned to: @SanskritiHarmukh on GitHub.

Hello,

The issue is pretty simple. Despite what the docs say, Authorization and Content-Type description headers are not disabled. The docs say that they are.

Steps to reproduce:
Go to docs
Read the note below the table
Open hoppscotch headers
Observe that they are not disabled.

Originally created by @yousefmarey12 on GitHub (Jan 9, 2025). Original GitHub issue: https://github.com/hoppscotch/docs/issues/274 Originally assigned to: @SanskritiHarmukh on GitHub. Hello, The issue is pretty simple. Despite what the [docs say](https://docs.hoppscotch.io/documentation/getting-started/rest/request-headers), Authorization and Content-Type description headers are not disabled. The docs say that they are. Steps to reproduce: Go to [docs](https://docs.hoppscotch.io/documentation/getting-started/rest/request-headers) Read the note below the table Open hoppscotch headers Observe that they are not disabled.

kerem closed this issue

2026-03-16 12:24:27 +03:00

kerem commented

2026-03-16 12:24:33 +03:00

Author

Owner

@SanskritiHarmukh commented on GitHub (Jan 9, 2025):

Thank you for pointing this out! It seems the note is missing the term "auto-generated," which is key to clarifying the behavior. When the Authorization and Content-Type headers are set through their respective fields, the description field for these headers becomes auto-generated and is therefore disabled for manual input. I'll make the necessary edits to the documentation and create a PR to address this.

@SanskritiHarmukh commented on GitHub (Jan 9, 2025): Thank you for pointing this out! It seems the note is missing the term **"auto-generated,"** which is key to clarifying the behavior. When the Authorization and Content-Type headers are set through their respective fields, the description field for these headers becomes auto-generated and is therefore disabled for manual input. I'll make the necessary edits to the documentation and create a PR to address this.