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.by mblancett - Nginx Mailing List - English
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 * About to connect() to localhost port 81 (#0) * Trying ::1... connected * Connecteby mblancett - Nginx Mailing List - English
We often proxy to hundreds of servers upstream, and because of the sheer number of instances we deal with, sometimes a server with a problem or a change may be re-provisioned and thus a dns response temporarily may not resolve. It would be very much appreciated if there were some configuration parameter to allow single members of a large pool of upstreams to not resolve in DNS without immediatelyby mblancett - Ideas and Feature Requests
I am looking for ways to target every Nth request into a very busy proxy within an nginx configuration. This particular proxy is extremely busy and receives POSTs to a single URI, and taking an approach like sharding by IP would not be the kind of traffic sample we’re after. The long term goal here is to replay some small amount (like 0.05%) of requests into a separate test environment. Curreby mblancett - Nginx Mailing List - English