mia-platform / mia-platform/custom-plugin-lib
isMiaHeaderInjected proxy headers if set in ADDITIONAL_HEADERS_TO_PROXY env
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When I set `isMiaHeaderInjected` option to false, the header to proxy set in `ADDITIONAL_HEADERS_TO_PROXY` env are proxied if I use the http client in the request object.
Furthermore, if I set the mia headers inside the `ADDITIONAL_HEADERS_TO_PROXY` list, them are proxied anyhow.
**Expected behavior**
I expect to not proxy headers if I set this option.
We have 2 possibilities:
1. `isMiaHeaderInjected` do not forward proxy if set
2. add another options, to avoid to proxy all headers and not only the headers flagged as mia-headers
**Desktop (please complete the following information):**
- Version: 6.0.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the HTTP client in the request object, using isMiaHeaderInjected=false and headers from ADDITIONAL_HEADERS_TO_PROXY. Trace how those options are handled for proxying, including Mia headers placed in the environment list. Done means the expected header-forwarding behavior is defined and verified for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100