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.
Experiencing random error 302 pages for anonymous users since upgrading to 6.x-1.20. Clearing the cache solves the problem, but it keeps recurring and I'm not yet seeing a pattern with intervals in which it's happening.
Any help would be appreciated.
Comments
Comment #1
bgm CreditAttribution: bgm commentedCan you check the contents of the cached page? (in cache/normal/...)
Are you using the crawler?
Are you using i18n?
Any redirect modules, such as globalredirect?
302 codes are usually for redirections. If it's the case, what was the source and destination of the redirection?
Comment #2
kruser CreditAttribution: kruser commentedThanks, now that I know what to look, when it happens again I'll check the cached page.
Are you using the crawler? No
Are you using i18n? No
Globalredirect? Yes
Comment #3
nelslynn CreditAttribution: nelslynn commentedHelp, happening here too after upgrade.
Are you using the crawler? No
Are you using i18n? No
Globalredirect? Yes
Using secure pages module.
Comment #4
kruser CreditAttribution: kruser commentedI'm also using secure pages
Comment #5
bgm CreditAttribution: bgm commentedSecurepages might be causing this. There are a few open issues in the queue regarding SSL.
Could you provide a simple config that I can reproduce? Ex: is the 302 on a secure page?
Was there a page generated in the cache when this occurred? What was its content?
Comment #6
nelslynn CreditAttribution: nelslynn commentedThere's no pattern as to what pages return 302. Some are views, some are nodes (simple content page). No secure pages produced a 302 error, however no secure page is set to cache via Boost.
Comment #7
philsward CreditAttribution: philsward commentedSame problem here:
Boost 1.20
Securepages 2.x-dev
Ran across this thread:
http://drupal.org/node/891620#comment-6036312
I haven't personally tried it yet but might fix the problem
Comment #8
philsward CreditAttribution: philsward commentedUpdate: The suggestion didn't work for me...
It might only apply to the 1.x branch of securepages
Update 2: K... the "fix" was actually for something different than the problem mentioned here... Sorry for the waste of space. I got excited when I saw a supposed fix...
Comment #9
philsward CreditAttribution: philsward commentedI will agree that the pages getting the 302 error is "random", but about every three times of hitting the "_0 Clear ALL boost cached data", I get the 302 on my about page or UC catalog page...