On 09/18/2007 07:40 PM, Roy T.Fielding wrote:
On Sep 18, 2007, at 6:46 PM, Plüm, Rüdiger, VF-Group wrote:
This works as designed. Please see the difference between the accept
headers sent by
IE6 and Firefox
IE6: Accept-Encoding: gzip, deflate
Firefox: Accept-Encoding: gzip,deflate
On tis, 2007-09-18 at 22:41 +0200, Ruediger Pluem wrote:
Agreed. Depending on the answers above we may need to have a list of headers
(like Accept-Encoding) where we compare the tokens in the field-value.
For all other headers we would stay with the plain compare we do today.
See also the
Hi,
I'm developing a webaccel project and I am trying to use apache to do that.
I'm choosing apache because squid does not support natively http/1.1
compression.
The main resources are: security (mod_security), saving bandwidth
(mod_deflate) and lowering backend servers load
-Ursprüngliche Nachricht-
Von: Fernando - Dfcom
Gesendet: Dienstag, 18. September 2007 16:18
An: dev@httpd.apache.org
Betreff: new webaccel appliance
debian:/cache# grep 'fd.jpg?' * -r
Binary file
3IT/6la/Omd/Jn@/287/BxY4K0g.header.vary/uaR/FRo/84M/RjT/oFp/MO
On Sep 18, 2007, at 6:46 PM, Plüm, Rüdiger, VF-Group wrote:
This works as designed. Please see the difference between the
accept headers sent by
IE6 and Firefox
IE6: Accept-Encoding: gzip, deflate
Firefox: Accept-Encoding: gzip,deflate
IE6 adds an additional space between gzip and
On tis, 2007-09-18 at 19:40 +0200, Roy T.Fielding wrote:
Argued? The space does not change the value of the field (which is
a comma-separated list). The question is really up to us as to how
much effort we make to compare the values for equality, since the
non-match just makes our cache
Nordstrom [EMAIL PROTECTED]
To: dev@httpd.apache.org
Sent: Tuesday, September 18, 2007 4:46 PM
Subject: Re: new webaccel appliance
Hello,
* Fernando - Dfcom [EMAIL PROTECTED] [20070918 22:06]:
In RFC 2616 I found:
An HTTP/1.1 server SHOULD include a Vary header field with any
cacheable response that is subject to server-driven negotiation
I don't know if removing Vary header is rfc-compliant, but resolves the
parse mistake).
Best Regards,
Fernando
- Original Message -
From: Andreas Kotes [EMAIL PROTECTED]
To: dev@httpd.apache.org
Sent: Tuesday, September 18, 2007 6:56 PM
Subject: Re: new webaccel appliance
Hello,
* Fernando - Dfcom [EMAIL PROTECTED] [20070918 22:06]:
In RFC 2616 I found
Hi,
Regarding this new webaccel project (hardware appliance) I was wondering
about some points:
- Use Freebsd S.O
- Tuning kernel and let it as small as possible.
- Enable Sendfile;
- Use AcceptFilter and accf_http
- --enable-nonportable-atomic=yes
10 matches
Mail list logo