Hi,

So i'm attempting to setup squid to interact with a hotspot/portal
system where squid uses deny_info to redirect users to a terms page.
Once they login their packets are marked and do not go through the
proxy anymore. However when i configure squid to use deny_info like
below it seems to cache the redirect in the users browser. So for
about 5-10 min after they have logged in and are no longer going
through the proxy they still get redirected every time they attempt to
go to that original requesting page.

cache deny all
...
acl whitelist dstdomain "/etc/squid/domains.lst"
deny_info http://login.domain.com/ whitelist
http_access deny !whitelist

I've tried using a url_redirector script to handle the redirect and
using 307 instead of a 302 code but both seem to be cached in browser.
Is there anyways to force the browser to not cache the redirect? or
perhaps another way to go about this? Example use case below, thanks
for any help/advise.

Example:
1. User opens web browser and requests http://xkcd.com
2. Request to http://xkcd.com is then redirected with a HTTP 302 code
to Login page.
3. User authenticates and accepts terms and conditions
4. User requests http://xkcd.com again after authenticating. They are
redirected back to the login page
5. All other webpages and domains work as expected with out problems.

Thanks,
Using squid 3.1.11

Reply via email to