PacketFence - BTS - PacketFence
View Issue Details
0000757PacketFencepublic2009-07-28 18:482011-01-26 15:43
obilodeau 
obilodeau 
normalminorhave not tried
closedfixed 
 
 
0000757: Redirect code causes browser to cache captive portal
Apparently, in a lot of setups the packetfence captive portal redirect page is cached for too long. Changing the redirect code from permanent move to 302 (temporary move) fixes a lot of the cases.

RewriteRule ^.*$ https://%%hostname%%.%%domain%%/cgi-bin/redir.cgi?destination_url=http://%{HTTP_HOST}%{REQUEST_URI} [^] [^] [L,R=302]

Could there be any regression with that?

TODO: I'll have to check mtn to see the design decisions of a redirect permanent vs temporary and also ask on the mailing list.
No tags attached.
Issue History
2009-07-28 18:48obilodeauNew Issue
2009-08-17 13:23obilodeauNote Added: 0001297
2009-08-19 15:55obilodeauStatusnew => assigned
2009-08-19 15:55obilodeauAssigned To => obilodeau
2009-10-26 16:39obilodeauNote Added: 0001373
2009-10-26 16:39obilodeauStatusassigned => resolved
2009-10-26 16:39obilodeauResolutionopen => fixed
2011-01-26 15:43obilodeauStatusresolved => closed

Notes
(0001297)
obilodeau   
2009-08-17 13:23   
I think that I am able to reproduce.

After a successfull registration, if I re-type the URL that I was trying to access the first time packetfence catches me with the captive portal for registration, it hangs there.

Probably that the IP / whatever info is cached because of the redirect type. I would need to change redirect type and see if I have the same behavior.
(0001373)
obilodeau   
2009-10-26 16:39   
Googled a bit and asked around here and found no reason not to use temporary redirect (302).

Fixed at monotone revision: 7af06e2fc36181b3f90320388d72cfff0938221d
http://mtn.inverse.ca/revision/info/7af06e2fc36181b3f90320388d72cfff0938221d [^]