To clarify, by 'illegal' I meant non-compliant.
These headers _are_ used, as we have run into them in production in our
business coming from clients, and some time on stack overflow shows these
are becoming more and more common. They are also RFC-compliant, and
competing products support them.
Po
Hello!
On Mon, Mar 19, 2018 at 07:05:43PM -0400, mblancett wrote:
> Nginx is reporting invalid incoming headers with RFC-compliant headers that
> use a '.' (meaning, a period) within the name.
Yes. Because, while being RFC-complaint, these headers cause
various problems, some are listed here:
Hello -
Nginx is reporting invalid incoming headers with RFC-compliant headers that
use a '.' (meaning, a period) within the name.
As an example, I am curling to a very basic proxy setup while trailing the
error log:
The following is valid:
# curl -vvvH "a-b-c: 999" localhost:81/test/v01
* Abo
