issuefiler comments

Results 45 comments of


                                            issuefiler

Disallow control characters in `user-id` and `password` to be RFC-compliant.

That’s right: RFC 2617 forbids all control characters but linear whitespace, and its successor, RFC 7617, simply forbids all of them including linear whitespace. Hence the original title of this...

Disallow control characters in `user-id` and `password` to be RFC-compliant.

If you don’t mind, may I change the title back?

Disallow control characters in `user-id` and `password` to be RFC-compliant.

And I believe it should return `undefined`, not `throw`, just like how invalid, malformed `Authorization` header field values are currently handled, so that it can be handled in the same...

Disallow control characters in `user-id` and `password` to be RFC-compliant.

I also doubt the need for “_an option for the parser to choose between the [RFC 2617](https://www.ietf.org/rfc/rfc2617.txt) and [RFC 7617](https://www.ietf.org/rfc/rfc7617.txt) modes_,” because, compared to [RFC 7617](https://www.ietf.org/rfc/rfc7617.txt), the characters that [RFC...

The build fails with GCC 12 due to the newly added `array-compare` warning.

``` CFLAGS=-Wno-array-compare CXXFLAGS=-Wno-array-compare ./configure ``` was my _temporary_ solution. But please, modify those parts of code to comply with the standard C++, rather than suppressing the warning.