Re: Proxying PHP Pages

From: David J N Begley <david@dont-contact.us>
Date: Sat, 12 Dec 1998 10:50:54 +1100 (EST)

On Fri, 11 Dec 1998, Henrik Nordstrom wrote:

> > 1. PHP pages aren't tied to ".php" extensions (some use ".php3", some
> > use ".phtml", &c.); and,
> >
> > 2. this site appears to throw ALL its pages through the PHP parser, which
> > means you'd have to add (gasp!) ".html" to your hierarchy_stoplist!
>
> hierarchy_stoplist is not about caching, it is about not wasting time in
> a cache hierarchy on uncacheable objects.

That's just the thing - if you're classifying PHP-generated objects as
"uncacheable" and determining this from the suffix, then you'll find PHP pages
on some sites not tied to that extension and (more importantly in this case)
for this particular troublesome site, would have to target the extension
".html" as being the trigger for PHP-generated objects.

IOW, it's not likely just a simple case of adding ".php" to the
hierarchy_stoplist and watching the problem disappear...

> Sites should provide correct expiry or cachability information on their
> dynamic content. If nothing is said then it is up to the cache
> implementation (or administrator) to decide by any form of heuristic
> algorithm of choice.

Ack!

dave
Received on Fri Dec 11 1998 - 16:41:46 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:38 MST