Yes. Or 127.0.0.1; either way. 
Sorry for dropping the ball.
It sounds to me like the issue will be resolved.
Thank you very much 
So to conclude, for X-forwarded-for to be included in the httpInclude request, the remote_ip address has to be set within the httpInclude call to an internal address like ::1 or 127.0.0.1.
Should I create an issue to track the progress on GitHub?
No; X-Forwarded-For is set by a proxy, not a template engine. The template engine will keep that header in httpInclude if it came in on the original request (i.e. from a proxy). It will not add that header.
But if that virtual request gets proxied, the proxy does need a RemoteAddr on the connection in order to set X-Forwarded-For.
So yeah, if you’d like to make an issue that should be a pretty easy one to fix 
Thanks again for all your help!
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.