Currently Being ModeratedAug 26, 2011 3:00 AM (in response to Enjolras)
Yes, I am experiencing this a lot also. I think hardly anyone has noticed it because its a fairly specific set of circumstances. I find it particularly annoying as our company-developed CMS uses HTTP-Auth and redirects a lot. So I have to reauth on every update.
Have you found a solution to this, or had any responses from anyone?
Currently Being ModeratedAug 26, 2011 11:13 AM (in response to Enjolras)
I was having the same issue with Safari 5.1 update on Snow Leopard, oddly I did not have this issue on a Lion upgrade from SL on my MBP.
I was able to resolve the issue by unchecking "User names and passwords" in the Auto fill portion of Safari's preferences. Quiting Safari, and then opening Safari again and then checking the "User names and passwords" option. Returning to the authentication page resulted in my user names and passwords returning to their auto fill simplicity.
Results may very, but I hope this can help.
Currently Being ModeratedAug 26, 2011 11:53 AM (in response to Enjolras)
Yes! That was happening to me with Facebook! I was wondering why that was happening. I use Snow Leopard but ever since updating to Safari 5.1 my Java doesn't work and I have been having odd behavior such as what you mentioned in your post. Ugh
Currently Being ModeratedSep 29, 2011 1:20 AM (in response to Enjolras)
Yep, having the exact same problem, and it's really annoying. Looking at the HTTP headers, it is definitely because of the 30x redirection. I've compared it against Firefox, and Safari is not sending the "Authorization: Basic" HTTP header with the authentication credentials in the GET directly after the 30x notification from the server. Because it's not getting the credentials, the server needs to get the client to reauthenticate. On normal GETs, Safari sends the Authorization header as expected. It only happens on a redirect.
I'm just wondering if it's related to this: http://lists.apple.com/archives/Webkitsdk-dev/2011/Mar/msg00006.html. Instead of fixing it, maybe they just stopped sending authorizations altogether on redirects.
I'm going to submit a bug report to Apple via the Safari "Report Bugs to Apple..." thingy. Fingers crossed it's fixed in an update shortly.
Currently Being ModeratedOct 12, 2011 8:05 PM (in response to mike.l.r)
It looks like today's release of Safari 5.1.1, which was included in the Mac OS X 10.7.2 update, has resolved this issue!
Currently Being ModeratedOct 17, 2011 3:25 PM (in response to Enjolras)
Correction—the problem still exists. It was not resolved by Safari 5.1.1.
Currently Being ModeratedOct 19, 2011 2:23 AM (in response to Enjolras)
I send a bugreport to apple about a very similar issue:
Currently Being ModeratedOct 31, 2011 12:49 PM (in response to Enjolras)
I'm getting this, too, using Safari 5.1.1. Thought it was my code, but found it was Safari. Unfortunately makes my web development impossible on Safari.
Currently Being ModeratedOct 31, 2011 2:01 PM (in response to dozy)
First I Reset Safari, then close Safari then navigate to:
Home/Library/Preferences and look for and then remove
Home/Library/Safari/ folder and remove the following two files:
Go to Home/Library/Caches/Metadata/Safari/ and remove the contents of that folder.
(These are just webhistory files and are not required for Safari to run. However, similar to preference files, problems can arise if they have become corrupt.)
Locate the cookies.plist file that's located in the Home/Library/Cookies/ folder and remove it.
They will all be recreated next time you launch Safari.
Currently Being ModeratedOct 31, 2011 2:07 PM (in response to worksafe)
You didn't say—does this resolve this particular problem? How is this different from using the "Reset Safari..." or "Empty Cache..." features built in to Safari?
Currently Being ModeratedJan 13, 2012 1:50 PM (in response to Enjolras)
I'm having this problem with Safari and an osCommerce store that I have behind http authentication. Does anyone know if this bug has been reported to Apple other than here?
Currently Being ModeratedJan 13, 2012 3:08 PM (in response to stevengking)
Yeah, I raised a bug report through the Safari "Report bugs to Apple..." menu item. That was a couple of months ago, and Safari has been updated once or twice since then with no fix. Of course, I got no feedback on my report. I guess if more people submit reports on this issue, it might get fixed.
Currently Being ModeratedJan 17, 2012 3:21 AM (in response to Enjolras)
Yes. I'm having a similar issue. I'm using Filemaker Pro's Web Viewer feature which uses the Safari webkit to render webpages in layouts and as it's dependent on Safari's settings, I'm having all sorts of problems with basic authentication.