PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000757 | PacketFence | public | 2009-07-28 18:48 | 2011-01-26 15:43 | |
| Reporter | obilodeau | ||||
| Assigned To | obilodeau | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0000757: Redirect code causes browser to cache captive portal | ||||
| Description | 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. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-07-28 18:48 | obilodeau | New Issue | |||
| 2009-08-17 13:23 | obilodeau | Note Added: 0001297 | |||
| 2009-08-19 15:55 | obilodeau | Status | new => assigned | ||
| 2009-08-19 15:55 | obilodeau | Assigned To | => obilodeau | ||
| 2009-10-26 16:39 | obilodeau | Note Added: 0001373 | |||
| 2009-10-26 16:39 | obilodeau | Status | assigned => resolved | ||
| 2009-10-26 16:39 | obilodeau | Resolution | open => fixed | ||
| 2011-01-26 15:43 | obilodeau | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||