Header casing changed when request it sent
See original GitHub issueI have a header in my configuration.
"headers": { "X-Hub-Signature":"sha1=9046ee408f8c902dec5c84760f59djkfhasjfh73" }
When watching the logs of the address I am testing the header comes through like X-hub-signature
.
The authentication system I am using requires the header be as defined as is instead of lowercased.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Are HTTP headers case-sensitive? - Stack Overflow
Header names are not case sensitive. From RFC 2616 - "Hypertext Transfer Protocol -- HTTP/1.1", Section 4.2, "Message Headers": Each header field consists ......
Read more >HTTP client request headers (lowercase) issue - Google Groups
A recent update changed how client request headers are sent to force all headers to lowercase. This is causing problems with some well-established...
Read more >If-Modified-Since - HTTP - MDN Web Docs
The If-Modified-Since request HTTP header makes the request conditional: the server sends back the requested resource, with a 200 status, ...
Read more >HTTP/1.1 Header Casing - Envoy Proxy
When handling HTTP/1.1, Envoy will normalize the header keys to be all lowercase. While this is compliant with the HTTP/1.1 spec, in practice...
Read more >RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
A client sends a request to the server in the form of a request method, URI, ... HTTP-date is case sensitive and MUST...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@maximillianus we have just merged a PR which adds an option for preserving header casing: #839 which is now available on the v1.6 branch - https://github.com/artilleryio/artillery/tree/v1.6.x It will be part of the next release, but in the meantime you can try running Artillery directly from that branch.
Is this error fixed on NPM [2.0.0-24] Version? I’m having the same issue.