Kong / Kong/insomnia

SSE requests don't include parent headers from folder

Open
#8,680 1 comment 0 reactions 0 assignees View on GitHub
B-bug S-unverified
Dominant language
TypeScript
Stars
40k
Forks
2.4k
Avg merge
2d 13h
Merged PRs (30d)
61

Description

### Expected Behavior

When an SSE request inside a folder with headers is executed, the headers from the parent folder should be included in the request.

### Actual Behavior

When an SSE request inside a folder with headers is executed, the headers from the parent folder are _not_ included in the request.

### Reproduction Steps

1. Create a folder
2. Add a custom header to it
3. Create a standard GET and an SSE request in the folder
4. Send each request
5. Observe that the standard GET request includes the header from the folder
6. Observe that the SSE request does not include the header in the folder

### Is there an existing issue for this?

- [x] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Which sync method do you use?

- [ ] Git sync.
- [ ] Insomnia Cloud sync.
- [x] Local only

### Additional Information

May or may not be related to https://github.com/Kong/insomnia/issues/8340. Interestingly enough, authorization that is set on a folder (via the Auth tab, not a direct header) _is_ included in the SSE request.

### Insomnia Version

11.1.0

### What operating system are you using?

Windows

### Operating System Version

Windows_NT x64 10.0.26100

### Installation method

Downloaded from Insomnia.rest, updated by the client

### Last Known Working Insomnia version

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by comparing a standard GET and an SSE request inside a folder with a custom header. Start at the SSE request path and compare its parent-header handling with the working GET path. Done means the SSE request includes the folder header while folder authorization and standard GET behavior remain intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.