Re: Supporting the Forwarded header (RFC 7239)

2017-08-08 Thread Maxim Dounin
Hello! On Tue, Aug 08, 2017 at 11:52:58AM +0300, Vasiliy Faronov wrote: > Hi Maxim, > > Thank you for your reply. > > > > I don't see how this is explicitly allowed by RFC 7239. > > In Section 4: > >A proxy MAY remove all "Forwarded" header fields from a request. Obviously enough, there

Re: Supporting the Forwarded header (RFC 7239)

2017-08-08 Thread Vasiliy Faronov
Hi Maxim, Thank you for your reply. > I don't see how this is explicitly allowed by RFC 7239. In Section 4: A proxy MAY remove all "Forwarded" header fields from a request. And in Section 6.2: The "unknown" identifier is used when the identity of the preceding entity is not known, b

Re: Supporting the Forwarded header (RFC 7239)

2017-08-07 Thread Maxim Dounin
Hello! On Sun, Aug 06, 2017 at 09:11:03PM +0300, Vasiliy Faronov wrote: > Hi nginx developers, > > As you know, RFC 7239 defines a Forwarded header to replace the zoo of > X-Forwarded-* with a single extensible syntax. > > There seems to be growing interest in deploying Forwarded. For > example

Supporting the Forwarded header (RFC 7239)

2017-08-06 Thread Vasiliy Faronov
Hi nginx developers, As you know, RFC 7239 defines a Forwarded header to replace the zoo of X-Forwarded-* with a single extensible syntax. There seems to be growing interest in deploying Forwarded. For example, aiohttp, a popular Python library, recently started reading Forwarded by default. I'd