FF5 is correctly caching redirects if the web server attaches cache headers. The SP needs an option to override Apache and set its own headers to expire the redirect so that the content its protecting can otherwise be set for caching.
I guess since it's possible to restore the original behavior if there's a problem with the same amount of effort, it wouldn't be too risky. Famous last words.
Former user
July 3, 2011 at 8:21 AM
Can ShibExpireRedirects be changed to default to "On", in 2.4.3 already? The risk of introducing a regression seems low to me, compared to the additional effort needed for users to reconfigure their Apache httpd (the ISAPI filter has been adding the Expires header for years, so I wouldn't expect new browser issues).
FF5 is correctly caching redirects if the web server attaches cache headers. The SP needs an option to override Apache and set its own headers to expire the redirect so that the content its protecting can otherwise be set for caching.