comment on

Just so this gets said...

If you use a "force content expiration" scheme that relies only on using a unique ID in the URL, you run a risk: If there is a caching proxy between the web server and some browser, that proxy's cache is going to hang on to otherwise expired content (i.e., prior unique IDs and their responses), and will spill valid content sooner, thus reducing the effectiveness of the cache.

To be friendly to caching proxy servers, use "Cache-control: no-cache" as part of your scheme.

By the way, caching proxy servers are starting to crop up all over. I'm seeing a lot of them near corporate firewalls, as a means for the corporation to better utilize bandwidth.

In reply to (dws)Re: CGI Caching question by dws
in thread CGI Caching question by chorg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks