Send original headers to the upstream

Kirill A. Korinsky kirill at korins.ky
Thu Jun 27 19:30:03 UTC 2024


On Thu, 27 Jun 2024 20:18:10 +0100,
Maxim Dounin <mdounin at mdounin.ru> wrote:
> 
> Well, this looks like highly specialized use case focusing on 
> non-guaranteed HTTP properties.
> 
> While it might be nice to support this use case as well, it seems 
> to be at most optional.  And I can't say I like the proposed 
> solution.
> 

It should defently be optional, and at least make differences between HTTP
headers that are added by Nginx and HTTP headers that are sent by the
client... seems like a good idea to me, doesn't it?

It makes things cleaner and allows to avoid injections of some unexpected
headers, like X-Real-IP, which might be used by complicated application by
some side effect.

P.S. I'm testing an updated patch, I think to send it soon.

-- 
wbr, Kirill



More information about the nginx mailing list