"Access Logs" with reverse proxy -> X-Forwarded-For

[rtoenniges]

Hi community,

I have a paperless-ngx server running which is using granian for the web frontend.
This server is behind a reverse proxy (nginx) and I've enabled the GRANIAN_LOG_ACCESS_ENABLED option.

So far this is working very well except for the issues that the client IP shows always the one from the reverse proxy.

In nginx I've enabled the following headers but with no success:

• Host
• X-Forwarded-Host;
• X-Forwarded-Server
• X-Real-IP
• X-Forwarded-For

Are there any configurations for granian to make it use the forwarded-for header?

[gi0baro]

Are there any configurations for granian to make it use the forwarded-for header?

As stated in the README:

Since none of the supported applications protocols define a strategy for proxies' forwarded headers, Granian doesn't provide any option to configure its behaviour around them.
What Granian provides instead, for contexts in which is being run behind a reverse proxy, are wrappers you can use on top of your application, in order to alter the request scope based on the headers forwarded by the proxy itself. You can find such wrappers in the granian.utils.proxies module

So, at the time being, the only way would be if paperless team use those wrappers in their codebase.
I guess you could also open a feature request here in the issues to have headers atoms in the access logs – since that it's your primary interest – but I can't make any promises in terms of ETA.

[rtoenniges]

Damn, how could I have missed this point in the readme :-O
Thank you for this answer,I think I will try to implement the wrapper in paperless.