[GH-ISSUE #3828] [bug]: Collection removes folder level headers from requests #1344

New issue

Open

opened 2026-03-16 19:55:31 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 19:55:31 +03:00

Owner

Originally created by @Stephen-Anderson-2000 on GitHub (Feb 14, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3828

Originally assigned to: @anwarulislam on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I create a request which is inside of a folder that is itself in a collection such as here:

And specify the authorization header at the collection level with some other custom header at the folder level it is possible to lose these folder level custom headers from the request.

Steps to reproduce

Create a collection and specify the authorization header (it can be anything, as long as it is specified)
Create a folder within this collection and add a different header
Create a request within the folder
View the headers tab for the request - it will look like this:
Go back to the collection headers and click "save" with or without making a change
Navigating back to the request and viewing the headers will show that it has lost the header applied by the folder:

Opening the folder level headers and clicking "save" will reapply the header - it wasn't deleted or lost from the folder it was just removed from the request.

Environment

Production

Version

Cloud

Originally created by @Stephen-Anderson-2000 on GitHub (Feb 14, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3828 Originally assigned to: @anwarulislam on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior When I create a request which is inside of a folder that is itself in a collection such as here: ![Screenshot 2024-02-14 164252](https://github.com/hoppscotch/hoppscotch/assets/47125566/2d2de3f2-497c-4f70-ad3b-67e01ed40b58) And specify the authorization header at the collection level with some other custom header at the folder level it is possible to lose these folder level custom headers from the request. ### Steps to reproduce 1. Create a collection and specify the authorization header (it can be anything, as long as it is specified) 2. Create a folder within this collection and add a different header 3. Create a request within the folder 4. View the headers tab for the request - it will look like this: ![Screenshot 2024-02-14 164501](https://github.com/hoppscotch/hoppscotch/assets/47125566/40974ef9-3db6-4ee3-9589-36c60104c60c) 5. Go back to the collection headers and click "save" with or without making a change 6. Navigating back to the request and viewing the headers will show that it has lost the header applied by the folder: ![Screenshot 2024-02-14 165636](https://github.com/hoppscotch/hoppscotch/assets/47125566/ba1dc77f-fac0-4530-ba1b-33671a519ffe) Opening the folder level headers and clicking "save" will reapply the header - it wasn't deleted or lost from the folder it was just removed from the request. ### Environment Production ### Version Cloud

kerem added the

bug

need testing

labels

2026-03-16 19:55:31 +03:00

kerem commented

2026-03-16 19:55:42 +03:00

Author

Owner

@anwarulislam commented on GitHub (Mar 5, 2025):

Hello @Stephen-Anderson-2000!
I was unable to replicate the issue by following the steps you provided. Please verify and confirm if the issue still persists.

@anwarulislam commented on GitHub (Mar 5, 2025): Hello @Stephen-Anderson-2000! I was unable to replicate the issue by following the steps you provided. Please verify and confirm if the issue still persists.