06, 2003 11:15 AM
To: Tomcat Developers List
Subject: Re: Http Connector / Gzip
Remy Maucherat a écrit :
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector
to
include/exclude
browser which could/couldn't use gzip
compression
?
May
Henri Gomez wrote:
Remy Maucherat a écrit :
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector to include/exclude
browser which could/couldn't use gzip compression ?
May be it could be use also to drop to HTTP 1.0 browser which
claims to be 1.1 compatible, but are not.
Remy Maucherat a écrit :
Henri Gomez wrote:
Remy Maucherat a écrit :
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector to include/exclude
browser which could/couldn't use gzip compression ?
May be it could be use also to drop to HTTP 1.0 browser which
claims to be
Well I take my inspiration from what is done in some TC 4.1 Valves...
I know ;-)
Some problematic stuff went away, though (the various mappers), but some
remain.
This feature would really need to be seriously optimized, as ideally
this would be enabled by default.
We could do better as
Henri Gomez wrote:
Could I commit my changes and start working on an optimizing version ?
Yes, of course. There's no big rush to start optimizing this ;-) (it's
really disabled by default, right ?)
Remy
-
To unsubscribe,
Remy Maucherat a écrit :
Henri Gomez wrote:
Could I commit my changes and start working on an optimizing version ?
Yes, of course. There's no big rush to start optimizing this ;-) (it's
really disabled by default, right ?)
Yes, since the restrictedUserAgents and restrictedUserAgents are set
Remy Maucherat a écrit :
Henri Gomez wrote:
Remy Maucherat a écrit :
+0 if disabled by default; -1 otherwise.
All this stuff is inefficient, as it uses Strings. Ie, we take the
byte array we have for the header value, convert it to a String, and
then regexp will likely convert it to something
Hi to all,
What about using regexp in HTTP 1.1 connector to include/exclude
browser which could/couldn't use gzip compression ?
May be it could be use also to drop to HTTP 1.0 browser which
claims to be 1.1 compatible, but are not.
CF: Apache HTTPD server
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector to include/exclude
browser which could/couldn't use gzip compression ?
May be it could be use also to drop to HTTP 1.0 browser which
claims to be 1.1 compatible, but are not.
CF: Apache HTTPD server
Well, I thought
Remy Maucherat a écrit :
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector to include/exclude
browser which could/couldn't use gzip compression ?
May be it could be use also to drop to HTTP 1.0 browser which
claims to be 1.1 compatible, but are not.
CF: Apache HTTPD
Some regex benchmark's I ran across:
http://tusker.org/regex/regex_benchmark.html
-Chad Johnson
-Original Message-
From: Henri Gomez [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 11:15 AM
To: Tomcat Developers List
Subject: Re: Http Connector / Gzip
Remy Maucherat a écrit
Gomez [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 11:15 AM
To: Tomcat Developers List
Subject: Re: Http Connector / Gzip
Remy Maucherat a écrit :
Henri Gomez wrote:
Hi to all,
What about using regexp in HTTP 1.1 connector to
include/exclude
browser which could
Peter Lin wrote:
interesting results. By any chance did you compare it
to Perl regexp to see the difference? :)
That would be interesting indeed :)
Do you know what the HTTPd uses, BTW ?
Remy
-
To unsubscribe, e-mail: [EMAIL
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 11:29 AM
To: Tomcat Developers List
Subject: RE: Http Connector / Gzip
interesting results. By any chance did you compare it
to Perl regexp to see the difference? :)
peter
--- Chad Johnson [EMAIL PROTECTED] wrote:
Some regex
14 matches
Mail list logo
