Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodejs sends headers in lower case but destination server ignores it #1380

Closed
LavrovArtem opened this issue Nov 21, 2017 · 2 comments
Closed
Assignees
Labels
AREA: server health-monitor STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@LavrovArtem
Copy link
Contributor

LavrovArtem commented Nov 21, 2017

Site: https://www.exblog.jp/
Script comes to client without content if hammerhead sends the user-agent header in lower case. Everything works right if we replace user-agent to User-Agent.

@LavrovArtem
Copy link
Contributor Author

Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.

https://tools.ietf.org/html/rfc7230#section-3.2

Also, RFC 7540 (HTTP/2):
Just as in HTTP/1.x, header field names are strings of ASCII
characters that are compared in a case-insensitive fashion.

https://tools.ietf.org/html/rfc7540#section-8.1.2

@LavrovArtem LavrovArtem reopened this Aug 10, 2018
LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Aug 10, 2018
@LavrovArtem LavrovArtem modified the milestones: Planned, Sprint #16 Aug 14, 2018
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
…s it` (close DevExpress#1380) (DevExpress#1719)

* fix `Nodejs sends headers in lower case but destination server ignores it` (close DevExpress#1380)

* add comment
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server health-monitor STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

1 participant