Re: Problems setting MIME Headers

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16947
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.Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Problems setting MIME Headers (Christer Olsson 1998)
  2. Re: Problems setting MIME Headers (Rob Marquardt 1998)
  3. Re: Problems setting MIME Headers (Rob Marquardt 1998)
  4. Re: Problems setting MIME Headers (Christer Olsson 1998)
  5. Re: Problems setting MIME Headers (Sandra L. Pitner 1998)
  6. Problems setting MIME Headers (Rob Marquardt 1998)
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.Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com Rob Marquardt

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:

New webdna.net host being considered ... (2004) BUG in [showif] using ^ (contains) (1997) Multi-processor Mac info ... (1997) problems with 2 tags (1997) Summing a field full of numbers ... (1997) help (2000) using showpage and showcart commands (1996) Passing Variables.. yikes, I'm dumb (2000) WC Database Format (1997) multi-paragraph fields (1997) WebCatalog can't find database (1997) my price won't move (1997) Re:listfiles-looking for slick solution (1997) WebCatalog can't find database (1997) Webstar 1.3.1 PPC (1997) mac hack (1997) Sort Order on a page search (1997) Hosting (2000) Hard Questions ? (1997) Separate SSL Server (1997)