You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app uses the nghttp2_asio library, and as it only speaks HTTP/2, it runs behind the nghttpx reverse proxy. As a result of that, all client connections effectively arrive via the same host+port combination to my app. I'm running nghttpx with the --add-forwarded=for flag so that my app can at least distinguish these requests from each other. However, I have no way to correlate the incoming request handled by nghttpx with what my application sees.
Can you please extend the available parameters in the access log formater within nghttpx so that the value that's used for the --forwarded-for=obfuscated is visible in nghttpx' access logs?
Note that using --forwarded-for=ip is not enough because the client port is not included. Even if it was included, that would still not be enough for me because the client connection can use HTTP/2 as well, and if that's the case, I cannot discriminate two requests which have arrived over the same TCP socket. The obfuscated value looks better in this regard.
The text was updated successfully, but these errors were encountered:
My app uses the
nghttp2_asio
library, and as it only speaks HTTP/2, it runs behind thenghttpx
reverse proxy. As a result of that, all client connections effectively arrive via the same host+port combination to my app. I'm runningnghttpx
with the--add-forwarded=for
flag so that my app can at least distinguish these requests from each other. However, I have no way to correlate the incoming request handled bynghttpx
with what my application sees.Can you please extend the available parameters in the access log formater within
nghttpx
so that the value that's used for the--forwarded-for=obfuscated
is visible innghttpx
' access logs?Note that using
--forwarded-for=ip
is not enough because the client port is not included. Even if it was included, that would still not be enough for me because the client connection can use HTTP/2 as well, and if that's the case, I cannot discriminate two requests which have arrived over the same TCP socket. The obfuscated value looks better in this regard.The text was updated successfully, but these errors were encountered: