I must say, this stumps me. I’m assuming it’s working for you somewhere? If Apache is in the mix, have you checked that the URL is sane (e.g. no trailing / bug or something)?

Can you run the tests on that setup? Or development mode?

Ok, just saw you added that it manifests with Safari. I’ll try that here (I generally use FF so that might explain why I didn’t notice it).

Is it working for you in Safari at devil.brightredglow.com? It’s working for me.

Yes! That is what is so perplexing. Why would it work at brightredglow.com, but not on my site? I haven’t had time to do any investigation since my posts a few days ago.

I’d suspect Apache and something with URL rewrites, but that’s just a WAG.

I just had a similar problem with an app I’m developing. A google search later, I came across this:

http://toolmantim.com/article/2006/9/19/safari_urls_the_semi_colon_and_one_night_in_paris

Or, the essential info:

I had the same problem on my test site (it worked fine for me locally). I was using http authentication to hide my test site from the world. and it turned out that safari wasn’t sending the authentication information if the semicolon is present in the URL so lighttpd was returning a 401 error. You can spot this in the server access logs (note the 3rd element, the username, is blank). (Tom Riley)

In both instances, the site was behind basic or digest auth.