I am investigating an unfortunate interaction between a Facebook feature (the "always use https" preference) and the behavior of certain browsers (definitely Mac Safari, perhaps others) when they receive an HTTP "302" redirect
( Read more... )
Clicking on any of the four links invokes a PHP script that uses a 302 redirect to another page. The difference between the four involves the processing of the fragment identifier -- the string after "#" in a URL.
"No old or new fragment" uses a link without an 'old' fragment identifier, and tells the PHP script not to add its own 'new' fragment identifier to the URL it redirects to.
"Old fragment only" uses a link with an 'old' fragment identifier, and tells the PHP script not to add its own 'new' fragment identifier.
"New fragment only" uses a link without an 'old' fragment identifier, but tells the PHP script to add its own 'new' fragment identifier when redirecting.
"Both old and new fragments" uses a link with an 'old' fragment identifier, but also tells the PHP script to add its own 'new' fragment identifier when redirecting
( ... )
Thanks again. My personal belief is that Firefox, Flock, and Chrome are behaving 'correctly', while Safari and Opera are both deviating in different ways from proper behavior. But in the absence of a formal standard, it's hard for me to say this definitively.
Clicking on any of the four links invokes a PHP script that uses a 302 redirect to another page. The difference between the four involves the processing of the fragment identifier -- the string after "#" in a URL.
"No old or new fragment" uses a link without an 'old' fragment identifier, and tells the PHP script not to add its own 'new' fragment identifier to the URL it redirects to.
"Old fragment only" uses a link with an 'old' fragment identifier, and tells the PHP script not to add its own 'new' fragment identifier.
"New fragment only" uses a link without an 'old' fragment identifier, but tells the PHP script to add its own 'new' fragment identifier when redirecting.
"Both old and new fragments" uses a link with an 'old' fragment identifier, but also tells the PHP script to add its own 'new' fragment identifier when redirecting ( ... )
Reply
#old
#new
#new
in firefox
""
""
#new
#new
in safari
""
#old
#new
#new
in flock
Reply
Reply
firefox 3.6.15
safari 5.0.3
flock 1.2.7
Reply
Reply
Reply
Reply
Reply
Reply
Old Fragment Only: ""
New fragment only: "#new"
old and new fragment: "#new"
Reply
Reply
Leave a comment