HTTP v1.1 Cache-Control headers in Apache v1.3.1 ......

HTTP v1.1 Cache-Control headers in Apache v1.3.1 ......

Post by Henny Bekk » Tue, 15 Sep 1998 04:00:00



Dear all,

Maybe I'm just plain stupid (sorry for that) but I wonder how to
configure apache v1.3.1 to generate HTTP v1.1 Cache-control headers
out of HTML files with META headers like:
   <META HTTP-EQUIV="Cache-control" CONTENT="private">

Cheers, Henny

--
-----------------------------------------------------------------------------

http    http://www.uu.nl/~henny   !             progress is not ignorance,but
PTT:    Voice: +31 30 2536971 Fax: +31 30 2531633 ! the illusion of knowledge

 
 
 

HTTP v1.1 Cache-Control headers in Apache v1.3.1 ......

Post by Marc Slemk » Tue, 15 Sep 1998 04:00:00



Quote:>Dear all,
>Maybe I'm just plain stupid (sorry for that) but I wonder how to
>configure apache v1.3.1 to generate HTTP v1.1 Cache-control headers
>out of HTML files with META headers like:
>   <META HTTP-EQUIV="Cache-control" CONTENT="private">

You don't.  META tags weren't designed to specify something the server
should parse and translate into a header.

 
 
 

HTTP v1.1 Cache-Control headers in Apache v1.3.1 ......

Post by Michael Fu » Tue, 15 Sep 1998 04:00:00




> >Maybe I'm just plain stupid (sorry for that) but I wonder how to
> >configure apache v1.3.1 to generate HTTP v1.1 Cache-control headers
> >out of HTML files with META headers like:
> >   <META HTTP-EQUIV="Cache-control" CONTENT="private">

> You don't.  META tags weren't designed to specify something the server
> should parse and translate into a header.

An alternative would be to build Apache with mod_headers and specify
the headers in your server config or an .htaccess file:

    http://www.apache.org/docs/mod/mod_headers.html

If memory serves, you could also write a fixup handler to parse META
tags and send the appropriate HTTP headers; the mod_perl module
Apache::HttpEquiv is supposed to be able to do something like this
but I've never used it.

--
Michael Fuhr
http://www.fuhr.net/~mfuhr/

 
 
 

HTTP v1.1 Cache-Control headers in Apache v1.3.1 ......

Post by Alan J. Flavel » Tue, 15 Sep 1998 04:00:00



Quote:> You don't.  META tags weren't designed to specify something the server
> should parse and translate into a header.

With respect, and in the interests of historical accuracy...

RFC1866 says:

 HTTP servers may read the content of the document HEAD to generate
 header fields corresponding to any elements defining a value for the
 attribute HTTP-EQUIV.

..and goes on to provide an actual example, of providing Expires,
Keywords, Reply-to, via such a META, and the corresponding server
headers that would result if the server supports this feature.

It's my impression that the original intention of META HTTP-EQUIV
had been to have them interpreted by the server.  This may very well
have been a poor idea, but you'll see that RFC1866 says a great deal
about what the server may or may not do with META HTTP-EQUIV, and makes
absolutely no mention AFAICS of a client ever paying the slightest
attention to them.

Of course, nowadays the situation seems to be very much the opposite,
and that may very well be a good thing.  Apache supports several ways of
assigning HTTP headers to any kind of document, not limited to HTML, so
all's well - so long as document providers are given proper access to
these facilities of the server that they use.

Sorry about that.

 
 
 

1. upgrading from v1.2.13 to v1.3.100, JDK, httpd

Here are all the packages and patches I needed to upgrade when moving
from 1.2.13 to 1.3.100. I wanted to get the Java JDK running on my
machine, hence the move. I also wanted a running NCSA httpd.

Do not expect 1.2.13 pcmcia, ppp, httpd or modules to work under 1.3.100
when you boot 1.3.100 the first time. You need to rebuild those pieces
and reboot a second time.

Hope this is useful,

        -Huw

--- configure, build, compile, install these in the listed order,
    then reboot for the 1st time into 1.3.100:

gcc 2.7.2 from ftp://sunsite.unc.edu/pub/Linux/GCC
libc 5.3.12 from ftp://sunsite.unc.edu/pub/Linux/GCC
ld.so.1.7.14 from ftp://sunsite.unc.edu/pub/Linux/GCC
binutils 2.6.0.14 from ftp://sunsite.unc.edu/pub/Linux/GCC
gdb 4.14 from ftp://sunsite.unc.edu/pub/Linux/GCC
linux 1.3.100 from ftp://sunsite.unc.edu/pub/Linux/kernel/v1.3

--- configure, build, install after rebooting:

modules 1.3.57 from ftp://sunsite.unc.edu/pub/Linux/kernel,
        with modules-1.3.57-patch from hhttp://www.pi.se/blox

procps-0.99a, with 1.3.91 patch applied,
        both from ftp://sunsite.unc.edu/pub/Linux/system/Status/ps
        may need to edit Makefile to build with BSD curses instead of ncurses;
        need to run the following perl one-liner on the diff to get a patch:
        perl -pi -e 's?build/procps-0.99a/??;'

termcap-2.0.8 from ftp://sunsite.unc.edu/pub/Linux/GCC,
        with references to obsolete type speed_t removed in termcap.[ch]

--- optional packages you may need to build, install after rebooting again:

pcmcia-cs 2.8.16 from ftp://hyper.stanford.edu/pub/pcmcia

ppp-2.2.0f from ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp,
        with the following perl one-liner run from the top directory in
        order to patch references to moved include files:
        perl -pi -e \
                's?net/ppp-comp.h?linux/ppp-comp.h?; \
                 s?net/if_ppp.h?linux/if_ppp.h?; \
                 s?net/ppp_defs.h?linux/ppp_defs.h?; \
                 s?net/pppio.h?linux/pppio.h?;' \
                `find . \( -name '*.c' -o -name '*.h' \) -print`


[ Huw Rogers     Senior Software Engineer, Fusion Systems Japan, Tokyo, Japan ]

--

[ Huw Rogers     Senior Software Engineer, Fusion Systems Japan, Tokyo, Japan ]

2. mod_perl

3. apache(https v1.3.6)-solaris-netscape-java1.2 problem

4. dtterm

5. v1.3 kernel, v1.5 httpd (NCSA) incompatibilities?

6. Daeron the liar. (Long Post---Sorry)

7. Kernels! v1.3.xx or v1.2.xx?!

8. virtual hosting on apache

9. SATAN v1.1.1 [released] and v1.1.4 [experimental] both do not compile on Redhat 6.0.

10. X386 v1.2e v1.0.2

11. Upgrading from Linux v1.2 to v1.3

12. different mod_rewrite behavior between v1.3.6 and v1.3.12??

13. SMP: v1.1 vs v1.4?