> I'm still wondering why mod_cache sets the expires header (or
> some other
> parameter, that causes the headers to be set).
Anything that goes in the cache has to have some expiration date--it can't
just live forever. The manual explains how its computed.
> And why GET and HEAD requests get
> now i change your sample rewrite rule abit to
> RewriteRule ^/(.*?)/(.*)$ /user/$2?user=$1 [L]
>
> When i tried to access http://www.example.com/me/home.jsp. i
> got the following error in error_log
>
> [error] [client 127.0.0.1] File does not exist: /var/www/html/me
>
> Seems httpd ignore th
> I just tried "curl -I
> http://news.dds.dk/uploads/pics/broenonline.gif"; and this is
> what I got:
> ...
> Note, HTTP/1.1 request and no Expires header.
Since I didn't get the Expires header, is it possible that some other device
like a proxy is adding this header to your request?
Allen
--
> I have discovered, that an Apache 2.2.3 server sets an
> "Expires" header on our static content.
>
> I suppose Apache won't set the header in a "clean" install,
> but which other module could cause this header?
from modules\http\http_filters.c, line 1008:
/*
* Control cachability for
> Now want when a user browse www.example.com/someusername/
> httpd will forward the request to
> www.example.com/user/?user=someusername
>
> And when browse a user browse
> www.example.com/someusername/login/ httpd will forward the
> request to www.example.com/user/login/?user=someusername
>
> I probably should have said this in
> the first place, most of these PDFs are hidden behind a
> login*, while a few of them are even paid-for. (And to make
> it even more complicated, PDFs become free after a while,
> while their location stays the same.) Apache knows -via a
> whole bunch of
> Let me guess.
>
> You're using the version of ReiserFS that changed the
> semantics of stat()?
Hello Nick,
The filesystem is ext3, running on top of Red Hat's standard LVM. This is
the default for a RHEL5 / CentOS5 installation.
Is anyone able to use strace to confirm that this either happe
> You would also have to change all links to the PDF's
> from www.yoursite.com/file.pdf to ...
Of you could setup www.yoursite.com/file.pdf to do a 301 or 302 redirect to
the new location of the PDF file. Both mod_alias and mod_rewrite can do
redirects. mod_rewrite can be more flexible but is mu
Hi Martin,
You could run two completely separate instances of httpd, one listening on
port 80 with MaxClients=100 serving your normal content, and the other
listening at port 8000 with MaxClients=20 serving your large PDF's. This
would require two completely separate http.conf files (for example,
Hello Sebastien,
Short answer: the host running HTTPS must have a dedicated IP address.
Long answer: when a client connects to the server at port 443, the first
thing they will do is an SSL handshake. This happens even before the client
sends its HTTPS request with the url and Host header. Ther
> Let me guess.
>
> You're using the version of ReiserFS that changed the
> semantics of stat()?
Hello Nick,
Its running whatever comes stock with a default installation of CentOS-5,
which is definitely not Reiser. If you think this is somehow relevant or
important, I'll try to figure out what
Summary:
When processing a "GET /.../file.html", Apache httpd briefly treats
file.html as a directory and attempts to open
"docroot/.../file.html/.htaccess". The os returns ENOTDIR, and then
processing of the request continues.
There would seem to be no reason for httpd to attempt to open
file.h
12 matches
Mail list logo
