In a recent Drupal project we turned on standard caching to help site performance. With this in place, however, we found that certain visitor-sensitive details might be revealed. For example, if a submission via the webform module contains an email address, and this is included somehow in the acknowledgement page (through custom code), then this custom page can be guessed for other users.
The reason for this is a complication of webform and fairly understandable custom-modular code.
Imagine you have a Drupal site: I have several, so that’s easy for me. Say you’ve got an index aggregating lots of your content in a listing, and it spans lots of pages. It’s probably a view created with the views module, slicing through your content in a special way.
Drupal has a core paging module that sorts out links along the lines of:
[« first] [< previous] [1] [2] [3] … [next >] [last »]