Posted by chawl on October 2, 2009 at 12:40pm
Jump to:
| Project: | http:BL |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | bryrock |
| Status: | closed (fixed) |
Issue Summary
How about page cache interaction, especially if minimum cache lifetime is imposed?
It seems that if a suspicious IP first visits a page, error is cached instead of content, thus error seems to be served for all anonymous users till page cache expires.
Also whitelist might not function properly as the visitor may be fooled by the cached error, though watchdog says "Session for *** whitelisted".
Now I have many anonymous log entries who try to whitelist themselves repeatedly, though they are successful, but are probably fooled by the cached error.
Sorry for a rather probabilistic issue, but I am not sure if I figured this out right.
Tx.
D 6.14
Normal caching
Check for all requests
Using HEAD from CVS
Comments
#1
I can't see how this happens, since the Drupal quits processing after printing the module's error message. Drupal has no chance to cache the page at all.
#2
Not entirely certain on this, but this issue looks to me like a casualty of the same problem identified here http://drupal.org/node/575906#comment-2051578.
As such, I believe this problem was corrected some time ago in the 6.x-2.x fork, and can be closed.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.