Header is send with illegal utf-8 characters
See original GitHub issueUsing http-server on a system with a German local produces headers with illegal utf-8 characters that are not accepted by some clients:
844424930447543-225-Fri Aug 28 2015 15:15:33 GMT+0200 (Mitteleurop�ische Sommerzeit)
The �
character is actually an ä
.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
How to pass a header with UTF-8 characters? - Stack Overflow
I'm trying to make a GET request in Postman where one of my header parameters has an UTF-8 encoded character like so:
Read more >UTF8 characters in HTTP headers - Google Groups
Hi,. Currently, if we get any utf8 (non-ascii but valid utf8) character in http header values, during the header parsing they ...
Read more >Setting the HTTP charset parameter - W3C
Hints on sending out character encoding information using the HTTP charset parameter. ... header('Content-type: text/html; charset=utf-8');.
Read more >Illegal Byte Code Character in Header Name | Imperva
An HTTP header name contains characters banned by HTTP standard. These are usually non-printable ASCII characters or other special characters (e.g. '<', '>', ......
Read more >Accept-Charset - HTTP - MDN Web Docs
UTF-8 is well-supported and the overwhelmingly preferred choice for character encoding. To guarantee better privacy through less configuration- ...
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
Can we make
Headers.Builder addLenient
public please? There may be some backends that support this, even if it’s not RFC-Conform I have to communicate with these legacy services.No problem! Yeah I’m trying to clean up all these old issues. I’m going to close for now, anyone who sees this again with an up-to-date http-server, please re-open right away!