Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Report ran and stated it was successful, even though site required basic auth. Check for www-authenticate header, if found return warning and abort.
Comment | File | Size | Author |
---|---|---|---|
#2 | site_audit-2064359-insights_detect_inaccessible_site.patch | 1.02 KB | xurizaemon |
Screen Shot 2013-08-13 at 10.02.24 AM.png | 40.07 KB | FluxSauce |
Comments
Comment #1
xurizaemonOn an htauth-protected URL using SSL, I see
Similarly using the server @ https://developers.google.com/speed/pagespeed/insights/ shows a 100% result but has a small warning at the top.
Comment #2
xurizaemonOK, this checks that the responseCode was 200. This does the right thing for 401 etc, but probably wants feedback.
Currently the insights report seems to handle redirects out of the box (good).
Should we permit people to run insights on their 404 pages though? Maybe that should be a switch so it's still available, but by default shows an error if the URL is typoed?
Comment #3
FluxSauce CreditAttribution: FluxSauce commentedI'd say this is a bug, not a feature request. Sorry about the delay, I'll get this in there.
Comment #5
FluxSauce CreditAttribution: FluxSauce commentedGood catch, thank you! I did a little cleanup afterwards.
Comment #6
xurizaemonThanks. IDK if you want a patch for it, but ... OMG unbalanced brackets!
The line above the last change in http://cgit.drupalcode.org/site_audit/commit/?id=0e19ea68f58cbdc0a8cde37...
Comment #7
FluxSauce CreditAttribution: FluxSauce commentedFixed, thanks again!