Previous 1 2 3 Next 31 Replies Latest reply: Mar 2, 2015 9:50 AM by RogWilco
Enjolras Level 1 Level 1

After upgrading to Mac OS X Lion, Safari 5.1 appears to not behave correctly with HTTP basic access authentication and server page redirects. Safari 5.1 is prompting for the username and password again on pages protected by HTTP basic access authentication, but only if those pages are the result of the server sending a 301 or 302 header to redirect to that page. Previous versions of Safari, and all othe current web browsers, do not prompt for the password again. I have confirmed this problem on three separate Macs running Safari 5.1.


A sample workflow:


  1. In Safari 5.1, visit a web site with HTTP basic access authentication in place
    HTTP basic access authentication can be configured on an Apache web server using directives such as "AuthType Basic" and "Require valid-user" either within the main server's configuration or inside a .htaccess file. It's typically used in conjunction with a .htpasswd file.

  2. Safari presents a sheet window asking for a username and password
    This only appears if it's the first time visiting the site since opening Safari. Log in with the username and password, click "Log in," and the page loads.

  3. Click a link to a regular page on the site
    The page loads. There's no re-entry of username and password required as expected.

  4. Click a link to a page that sends a 301 or 302 "moved" header to redirect the browser to another page
    The sheet window appears in Safari asking for the username and password again.


This behavior is incorrect.


For reference, Safari's "AutoFill web forms" is checked in the Preferences window; however, I do not check the "Remember this password in my keychain" checkbox in the sheet window Safari produces to enter the username and password for HTTP basic access authentication.


Oddly, a lot of my day-to-day web development has this scenario which renders Safari 5.1 unusable at this time. I have been unable to find anyone else mentioning this issue.


Has anyone else also noticed this?

Safari, Mac OS X (10.7)
  • andy-tibus Level 1 Level 1

    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?

  • nicksageek Level 1 Level 1



    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.



  • skeeterpod Level 1 Level 1

    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

  • mike.l.r Level 1 Level 1

    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: 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.

  • Enjolras Level 1 Level 1

    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!

  • Enjolras Level 1 Level 1

    Correction—the problem still exists. It was not resolved by Safari 5.1.1.

  • pterrettaz Level 1 Level 1

    I send a bugreport to apple about a very similar issue:

  • dozy Level 1 Level 1

    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.

  • worksafe Level 2 Level 2

    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.

  • Enjolras Level 1 Level 1

    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?

  • chistomax Level 1 Level 1

    no, it doesn't resolve the problem

  • stevengking Level 1 Level 1

    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?

  • mike.l.r Level 1 Level 1

    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.

  • Stupidflippincomputers Level 1 Level 1

    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.

Previous 1 2 3 Next