Most CGI scripts or their servers include a header that defines the page given from the CGI as a no-cache page. Couple that with a specific expiration date (generally a date that has already passed so that no-caching ever happens) and you have those issues.
I believe the headers usually come from the cgi. But, sometimes the server will tack that on for cgi executions. So, depending on the lib you are using (if any), you should be able to change the CGI.
There is one thing I don't understand. Somehow servers respond differently to SSI, PHP, mod_perl or CGI generated pages. Search engines will not cache these pages, even though no headers are specified. Ditto goes for browsers. I think certain servers might add some header crap-o in. I would like a little insight on this if anyone has a clue.
-
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.
|
