Closed (fixed)
Project:
System Status
Version:
7.x-2.6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
13 May 2014 at 15:19 UTC
Updated:
20 May 2014 at 17:45 UTC
Jump to comment: Most recent
Please add possibility to work with sites behind http auth password.
Comments
Comment #1
sam hermans commentedYes,
I noticed this the last few weeks that a lot of people are adding sites protected by basic authentication. This has been added in the issue queue of the website and will be live soon.
Comment #2
kpa commentedYou can do this in the apache conf setup for the site. We're using
Comment #3
sam hermans commentedHmm .. maybe even a better idea.. that way we can keep the 'site configuration parameters' to a minimum..
FYI: The IP specified is correct, but the hostname of the service that fetches your site is 'status.drupalstatus.org'
I'm going to add your configuration example to the FAQ for now.
Comment #4
dmitrii commentedI'm tried .htaccess/server config solutions before support request creation. but it doesn't work for me.
probably it's maybe virtualmin specific problem
Comment #5
sam hermans commentedNo worries, i'll add it tomorrow .. it was quite busy last few days so i had no time for this project.
I'll post here when it's ready for testing.
Comment #6
dmitrii commentedThanks!
I'll test new feature with pleasure.
Comment #7
sam hermans commented@dmitrii i have just updated the website, this should now show the HTTP code we recieve when trying to fetch your module list.
Can you confirm that you now see those codes ? My tests locally show that you should get the 401 (Unauthorized) response when using .htaccess require-valid-user
Comment #8
dmitrii commentedI'm confirm.
Our service recieved the following HTTP code: 401
The 401 (Unauthorized) response typically means that this site is protected by some kind of IP-firewall or authentication.
Comment #9
sam hermans commented@dmitrii Okay, the functionality should be there .. can you give it a try and let me know what your results are ?
Comment #10
sam hermans commentedComment #11
dmitrii commentedSam, thanks.
Dashboard and Modules pages work now.
But https://www.drupalstatus.org/user/sites page crashed with "Whoops, looks like something went wrong." message.
Also site's page crached for protected sites (e.g. site id 10128). For non protected sites service is working.
Comment #12
sam hermans commentedHeh, for some reason the protected site you added does not report it's current core version .. As this is used on various pages to display the Drupal version, these pages crash.
Are you using an alternative distribution like drupalcommerce ?
Comment #13
dmitrii commentedYes. The site starts with flight profile and later mixed with pantheon profile. I'll take a look inside your module for this site.
Also I added protected d6 site - it works.
Comment #14
sam hermans commentedI just noticed that in the Drupal module you have the possibility to NOT report core modules, do you have this option selected or not ?
Either way i will modify the site so that everything still works even if you do not report drupal core version.
Comment #15
dmitrii commentedAll options are selected for System Status module.
Comment #16
sam hermans commentedSo i fixed all errors on the webinterface that can be caused when the drupal version is not reported. I'm going to close this issue since the basic authentication works fine, and open another for the core versions..
https://drupal.org/node/2271197