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:
[Sum] function? (1997)
Keep away (1997)
Emailer help....! (1997)
[WebDNA] Product Search Algorithm (2013)
Email encryption (1998)
Inventory Adjustment (2000)
Merging databases (1997)
[WebDNA] Store module/site (2012)
[WebDNA] Talklist Archive & Twitter (2009)
return missing item (was:WebCat Sales) (1997)
Exporting from Excel (1998)
CommandSecurity? (1997)
WebDNA and FTP (2003)
Re:redirect from the errorsMessages.db entry (1997)
PCS Frames-Default page is solution! (1997)
Practice runs ? (1997)
Opposite of Summ=T? (2000)
Hello world ... (2002)
Fun with Dates - finally resolved but.... (1997)
WebCatalog [FoundItems] Problem - LONG - (1997)