🚀 go-pugleaf

On 08 Feb 1999 09:08:01 +0000, Graham Murray <graham@barnowl.demon.co.uk> wrote:
>Tony Finch <fanf@demon.net> writes:
>
>> Complain to the webmaster of the site because it's their fault if they
>> don't provide appropriate Expires: headers.
>
>Is that the Webmaster responsible for the content of the site, or that
>of the site which hosts/serves the pages? Many (probably most)
>organizations do not host their own web pages. 

In general, there will be ways of achieving this with commercial 
web-hosting services.  I can think of three ways I might do this on 
demon's ComWeb solutions (although I'd have to go read up on which 
would work)

>For Demon homepages, is there any way that the customer can set the
>Expires: header so that other caches will correctly refresh (I know
>that the customer can (and should) force the Demon caches to refresh
>when a page is updated)? Will setting a Meta tag with the expires
>work, or does it have to be set in the server?

If you mean `META http-equiv' tags, then they aren't parsed by caches
or servers, and they're not equivilent to any http header, despite
their really stupid name.

They are parsed by browsers, sometimes.  Even less often they're
parsed by browsers in a non-broken manner...

If you want more than a bare-bones web server, I suspect you ought to
pay for it... but that's just me.

>[crossposted to demon.homepages.authoring because that is where the
>question is relevent]


-- 
"On a normal ascii line, the only safe condition to detect is a
'BREAK' - everything else having been assigned functions by Gnu
EMACS."
	-- Tarl Neustaedter