Re: Problems setting MIME Headers
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16957
interpreted = N
texte = >On 4/8/1998 9:11 AM, Christer Olsson so noted... > >>>[setMIMEHeader name=Cache-control&value=proxy-revalidate] >>> >>>Which should cause the proxy to revalidate at each request. >>>Unfortunately, when I list the MIME headers on the page, I get: >>> >>>12) Cache-control = Max-age=259200 >>> >>>Which is the same as if I'd done nothing at all. I've also tried >>> >>>[setMIMEHeader name=Cache-control&value=max-age=0] >>> >>>and would rather use, but it also appears to have no effect (is there a >>>problem by having an = in the value definition?) >>> >>>Is there someplace special the [setMIMEHeader] needs to be placed? Anyone >>>able to get something like this to work? >> >> >>Cache-control is a HTTP/1.1 header - is your server HTTP/1.1. >> >>For HTTP/1.0 you could try: Pragma: no-cache or Expires: 0 for avoiding >>caching. > >Yes, our server's HTTP/1.1 compliant, but I've also tried Expires: 0 with >the same (non-) result.OK. But that won't help if the client is issuing a GET HTTP/1.0 request. In that case the server is supposed to answer with a HTTP/1.0 header. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se
Associated Messages, from the most recent to the oldest:
>On 4/8/1998 9:11 AM, Christer Olsson so noted... > >>>[setMIMEHeader name=Cache-control&value=proxy-revalidate] >>> >>>Which should cause the proxy to revalidate at each request. >>>Unfortunately, when I list the MIME headers on the page, I get: >>> >>>12) Cache-control = Max-age=259200 >>> >>>Which is the same as if I'd done nothing at all. I've also tried >>> >>>[setMIMEHeader name=Cache-control&value=max-age=0] >>> >>>and would rather use, but it also appears to have no effect (is there a >>>problem by having an = in the value definition?) >>> >>>Is there someplace special the
[setmimeheader] needs to be placed? Anyone >>>able to get something like this to work? >> >> >>Cache-control is a HTTP/1.1 header - is your server HTTP/1.1. >> >>For HTTP/1.0 you could try: Pragma: no-cache or Expires: 0 for avoiding >>caching. > >Yes, our server's HTTP/1.1 compliant, but I've also tried Expires: 0 with >the same (non-) result.OK. But that won't help if the client is issuing a GET HTTP/1.0 request. In that case the server is supposed to answer with a HTTP/1.0 header. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se
Christer Olsson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
HTTP upload (2000)
[searchString] (1997)
show all problem (1997)
[WriteFile] problems (1997)
Summing fields (1997)
relogin same user? (1998)
Garbage display after 100 records (was WebCatalog usage) (1997)
Problems with [Applescript] (1997)
MISTAKE in last post: Adding multiple items to Cart (1999)
I have observed and I am gone. (1998)
Moment of Thanks (1997)
webcat2b12 CGI -- Date comparisons (1997)
Email (1998)
webcat error log (1998)
Template transformed itself into a database? (1998)
WebCatalog for guestbook ? (1997)
PC Auth Hub+Merchant (1998)
wo search help (1999)
$Quit, $CloseDatabase corrections (1997)
ConvertChars (2000)