Expired pages/disabling caching?

[Mike Selner]

I'd like to mention that this is a fairly large problem for us, too.

My current work-around is to add some artificial information (a serial
number) to the url, to fool omniweb.  Not a good thing.

The answer, I would think, depends on if the expiry of documents is
part of the http standard, and if OmniWeb plans to follow the standard.

>
>  Since I've seen no answers to my original message, I'm assuming it
>  somehow got lost in the "Foundation controversy" argument.
>
>  > I'm writing a WWW server that programmically generates pages.
>  > I'd like to be able to use
>  > Expires: Sunday, 01-Jan-95 00:00:00 GMT
>  > as a header to disable caching for certain URLs. However, Omniweb 1.0
>  > appears to ignore the "Expires:" header. Is this true or am I
>  > overlooking something?
>
>  Well, I have been able to verify that this works for Netscape, so I'm
>  assuming that Omniweb 1.0 just doesn't support it.  In that case, can
>  anyone answer the following question?
>
>  > If the header is currently ignored, is there a way to disable caching
>  > altogether for Omniweb 1.0?
>
>  -Mike Kienenberger
>   Arctic Region Supercomputing Center
>   mkienenb at arsc.edu
>