We presently possess a directory that is password-protected while using Apache BasicAuth module, via .htaccess along with a linked .htpasswd file. For a while, it has performed without error, however lately Google Chrome alone has started responding poorly towards the configuration.
This is exactly what happens:
From Google Chrome, the consumer visits the link to your directory that is password-protected via BasicAuth. Upon the entry of the correct account information, Google Chrome immediately reviews that "The web page isn't available." The mistake code is "Error 15 (internet::ERR_SOCKET_NOT_CONNECTED): Unknown Error", as though moving to some non-existent server.
Once the user refreshes the page, however, it loads perfectly as though nothing happened. Not one other problems occur before the user restarts the browser, navigates for this URL again, and it is instructed to re-enter their BasicAuth account information. Again, to date as possible tell, this error happens only in the search engines Chrome.
This continues to be recognized in a variety of different iterations of Chrome version 11..696.*.
Based on if the user accesses your directory under consideration with no trailing-forward slash (we're using mod_rewrite within this situation), the HTTP response was formerly either a couple of redirects. (Going to the URL with no trailing forward-slash redirects the browser towards the URL having a trailing forward-slash.) We've since removed the requirement for the 2nd redirect, which reduced the problem for many customers, however other customers go through the error with and without an HTTP redirect following a BasicAuth login.
Any assistance and/or insight could be greatly appreciated.
The appropriate lines in our .htaccess file:
<Limit GET POST>
RewriteCond % -s [OR]
RewriteCond % -l [OR]
RewriteCond % -d
RewriteRule ^.$ - [NC,L]
RewriteRule ^.$ ./index.php [NC,L]
Just observed it's a pending problem on Chrome browser although it was reported to occur on particular OS. Password protected directory appears to become a supply of error within this situation. Still suffering myself:(
You might keep monitoring in the search engines forum to determine contrary has enhanced:
This bug continues to be inherited since past few releases.
Hope Google men can sort this out soon.
* Please Click Here and STAR this Problem (Top-Left). It's among the best and many official methods to get this to bug a greater priority. http://code.google.com/p/chromium/issues/detail?id=57082
Google will fix this problem with v 12 http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/0ab925f21cacd3bb/3fcfa23ae7182102?lnk=raot&pli=1