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.
Boost works great.
If I use http://drupal.org/project/securepages and select the option, "Switch back to http pages when there are no matches", I get the following error message when I go to admin/reports/status
"Boost crawler did not get a 200 response; 302 returned instead."
Is this a bug or a feature? Should I be brining this up over at securepages?
Comment | File | Size | Author |
---|---|---|---|
#1 | boost-891620.patch | 1.09 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedupped the redirect counter from the default 3 to 10
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted
Comment #3
johnthomas00 CreditAttribution: johnthomas00 commentedThis did not solve the problem for me.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedWell a 302 is a redirect; so this might be in a redirect loop...
Comment #5
johnthomas00 CreditAttribution: johnthomas00 commentedAgreed, not sure how to fix, but probably not a boost problem, so marking
Comment #6
picou-1 CreditAttribution: picou-1 commentedI am getting the exact same error has anyone solved this issue?
Comment #7
dirtysteak CreditAttribution: dirtysteak commentedHaving the same problem.
Over at secure pages they are saying this is a boost problem or an .htaccess problem
http://drupal.org/node/443896
Any ideas?
Comment #8
Fabianx CreditAttribution: Fabianx commentedQuite easy to fix:
Not sure if that is the best fix, but I don't think all URLs should hit https from localhost everytime ...
Comment #9
Wolfflow CreditAttribution: Wolfflow commentedsubscribe. for my similar issue look here: http://drupal.org/node/1111374
Comment #10
RandallKent CreditAttribution: RandallKent commentedWould love to see @Fabianx patch applied.
Comment #11
RandallKent CreditAttribution: RandallKent commentedComment #12
nelslynn CreditAttribution: nelslynn commentedI get the same error message with the latest Boost Dev (Dec 23), and securepages module. Patch with #8 removes error on the Status Report page, but no cache pages are created.
Boost with boost crawler works fine with uc_ssl module (with one minor issue), but not securepages.
Any guidance to get the boost crawler working with securepages?
Comment #13
boosh CreditAttribution: boosh commentedAdding "boost-crawler" to the list of "Ignore pages:" did the trick for me. I'm using 6.x-1.18, though I would suspect that it would work just as well for 6.x-1.x-dev too.
Comment #14
bret.miller CreditAttribution: bret.miller commentedThanks boosh! Adding "boost-crawler" to the list of "Ignore pages:" in the Secure Pages configuration took care of the error for me too on 6.x-1.20.
Comment #15
philsward CreditAttribution: philsward commentedI wish I could say the same to suggestion #13...
boost 1.20
securepages 2.x-dev
Any other ideas?
Comment #16
philsward CreditAttribution: philsward commentedYa know, after re-reading the initial issue, I've realized the problem I have isn't directly related...
Here is the issue to the problem I am experiencing:
https://drupal.org/node/1618030
Comment #17
bgm CreditAttribution: bgm commentedI'd rather avoid the patch in #8 because of the testing it would take to be sure it does not break other sites.
If we can solve this by a configuration change in securepages, and it is specific to securepages, then I added a "requirement" check instructing people to review their configuration and make sure they have "boost-crawler" in the ignored pages.
Committed to 6.x-1.x, will be in Boost >= 6-x.1.21.
Comment #18
kimadamson1 CreditAttribution: kimadamson1 commented#13 fix did it for me with Boost 6x-1.9 and Secure Pages 6x-1.2. Thank you!
Comment #20
WeRockYourWeb.com CreditAttribution: WeRockYourWeb.com commentedExperienced this same problem. The fix at #13 appears to work at first but then we had the same issue. The only foolproof solution was to downgrade to securepages 6.x-1.9.