IP restriction behind Squid reverse proxy

Hi,
Is it possible to use the IP restriction (as in User belonging to a Usergroup based on IP condition) when being behind a reverse Proxy? Apache seems to log only the IP of the Squid box.



Is there a way for Matrix to check the X-Forwarded-For header? Or is there simpler and I've missed it?



Cheers.

Currently, no. Matrix only looks at the standard HTTP headers and will always see Squid IP address.


You may submit a feature request to get Matrix to look at alternative headers.

[quote]Currently, no. Matrix only looks at the standard HTTP headers and will always see Squid IP address.


You may submit a feature request to get Matrix to look at alternative headers.

[right][post=“12506”]<{POST_SNAPBACK}>[/post][/right][/quote]

See, my question above needs to be combined with the HTTPS for single page. When I first noticed this problem, my understanding was that we would tell users that if they wanted IP restricted pages, they would simply set it to be HTTPS. In our architecture, HTTPS goes directly to the App therefore the IP Restriction would work without a glitch.



I guess a feature request will probably occur one way or the other… maybe both.



edited: The link to the post was wrong…