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... )
We're running some sort of web server on olum.org. "ps" reveals some apache processes with happy looking arguments like "-DHAVE_PHP5". But I don't have any idea how to test if it works. You could email me a tar or zip file with some contents and I could put it up as http://www.olum.org/yduj/ron and you could do whatever you wanted. Well, within reason ;-)
For others interested in helping, it's now up at http://www.olum.org/yduj/redir_frag. Have fun, and report your browser version and the results you got from the four tests. I did IE 8 and FF 3.6 on a PC and a really old FF 3.0 on linux. And lynx, just for grins.
Old fragment only: "" in Safari 5.04; "#old" in Firefox 3.6.15, Camino 2.0.6, Chrome 10.0.648.133, and Opera 11.01. I consider Safari's behavior to be broken.
New fragment only: "#new" in all my browsers
Both old and new fragments: "#old" in Opera, "#new" in Safari, Firefox, Camino, and Chrome. I wonder why Opera is choosing different behavior from the others.
Thanks. So IE also behaves (in my opinion) wrongly, and Safari may have just copied that behavior.
I don't know whether it is possible to run more than one version of IE on a PC. If you have other versions of IE around (9, 7, 6), can you try them as well?
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
( ... )
Comments 25
Reply
Reply
Reply
No old or new fragment: "" in all my browsers
Old fragment only: "" in Safari 5.04; "#old" in Firefox 3.6.15, Camino 2.0.6, Chrome 10.0.648.133, and Opera 11.01. I consider Safari's behavior to be broken.
New fragment only: "#new" in all my browsers
Both old and new fragments: "#old" in Opera, "#new" in Safari, Firefox, Camino, and Chrome. I wonder why Opera is choosing different behavior from the others.
(What results did you get from your tests, Judy?)
Reply
FF (both): "" "#old" "#new" "#new"
Reply
I don't know whether it is possible to run more than one version of IE on a PC. If you have other versions of IE around (9, 7, 6), can you try them as well?
Reply
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
(The comment has been removed)
Reply
(The comment has been removed)
Reply
Leave a comment