DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23643.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23643.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23643.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23643.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23613.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
hgomez 2003/10/07 01:48:38
Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
http11 build.xml build.properties.sample
Log:
Add regexp support to check for Compression/HTTP 1.1 compatible browsers.
Revision Changes
hgomez 2003/10/07 01:48:50
Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java
Log:
Add regexp support to check for Compression/HTTP 1.1 compatible browsers.
Revision ChangesPath
1.42 +7 -0
Shouldn't we upgrade TC 4.1 and JTC to regexp 1.3 ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
hgomez 2003/10/07 02:01:57
Modified:.build.properties.default
Log:
Update to get regexp
Revision ChangesPath
1.2 +9 -1 jakarta-tomcat-connectors/build.properties.default
Index: build.properties.default
hgomez 2003/10/07 02:04:27
Modified:.build.properties.default
Log:
Oups, no need for it
Revision ChangesPath
1.3 +1 -9 jakarta-tomcat-connectors/build.properties.default
Index: build.properties.default
What about the idea to add notes in HTTP 1.1 connector ?
It will mimic the way HTTPD teams using BrowserMatch :
- Disable HTTP 1.0 for some browsers
BrowserMatch Mozilla/2 nokeepalive
BrowserMatch MSIE 4\.0b2; nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch RealPlayer 4\.0
Hello,
I'm testing the Tomcat-Deployer (Version 5.0.12 and 5.0.13). Both
returns an error when i want to deploy the generated war file.
The error is:
The deploy task doesn't support the update attribute.
Is the Deployer ever tested?
Whats the error?
Best regards
Thorsten Kamann
--
Thorsten
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,
On Mon, 06 Oct 2003 16:57:09 +0200
(Subject: [Fwd: Re: /www/www.apache.org/dyn/mirrors/mirrors.cgi])
jean-frederic clere [EMAIL PROTECTED] wrote:
After having some problems with the ant download task. I have thought of 2
ways to improve it.
1 - Use a mirror via a modified mirrors.cgi.
Thorsten Kamann wrote:
Hello,
I'm testing the Tomcat-Deployer (Version 5.0.12 and 5.0.13). Both
returns an error when i want to deploy the generated war file.
The error is:
The deploy task doesn't support the update attribute.
Is the Deployer ever tested?
Yes.
Whats the error?
It (obviously)
Hi...
I am using apache 2.0.47, tomcat 4.1.27 integrated with mod_jk2 2.0.2 on
a RedHat 9
It works fine, but sometimes (usually when power crash), the apache can
not find tomcat when restarting the machine. Im error.log of apache2, I
have these errors:
[Mon Oct 06 11:24:21 2003] [notice]
Hello Remy,
Remy Maucherat wrote:
Thorsten Kamann wrote:
It (obviously) works for me.
Yes, that was my error. I've used an ant installation with an old
catalina-ant. Then the error occured.
Now its wonderful :)
I've extended the build.xml out of the Tomcat-Deployer-project. Now the
build.xml
Thorsten Kamann wrote:
Hello Remy,
Remy Maucherat wrote:
Thorsten Kamann wrote:
It (obviously) works for me.
Yes, that was my error. I've used an ant installation with an old
catalina-ant. Then the error occured.
Ah, ok.
Now its wonderful :)
I've extended the build.xml out of the
remm2003/10/07 06:25:45
Modified:.build.properties.sample
Log:
- Update some dependencies.
Revision ChangesPath
1.68 +6 -6 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
remm2003/10/07 06:27:38
Modified:.RELEASE-NOTES-4.1.txt
Log:
- Changelog update for 4.1.28.
Revision ChangesPath
1.80 +48 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
Index: RELEASE-NOTES-4.1.txt
[EMAIL PROTECTED] a écrit :
remm2003/10/07 06:25:17
Modified:catalina/src/conf server.xml
Log:
- The connector class being used by Tomcat 4.1 doesn't have the
appropriate setters, nor the set-any-property mod that is in 5.0.
As a result, the example won't work right now
hgomez 2003/10/07 07:28:34
Modified:http11 build.xml build.properties.sample
.build.properties.default
Log:
Update to regexp 1.3 (and fix download location)
Revision ChangesPath
1.16 +2 -2 jakarta-tomcat-connectors/http11/build.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
jfarcand2003/10/07 07:38:12
Modified:catalina/src/conf server.xml
Log:
Make the xmlValidation more visible so people (meaning I) don't forget to turn on
those attributes when testing.
Revision ChangesPath
1.25 +4 -13
Henri Gomez wrote:
[EMAIL PROTECTED] a écrit :
remm2003/10/07 06:25:17
Modified:catalina/src/conf server.xml
Log:
- The connector class being used by Tomcat 4.1 doesn't have the
appropriate setters, nor the set-any-property mod that is in 5.0.
As a result, the example
Henri Gomez wrote:
Remy Maucherat a écrit :
Did the build works (since there is now the regexp 1.3 floating around) ?
Yes, I had it in my build.properties before (since the sample resource
is just a sample, rather than a defaults list, they are often out of sync).
I don't have the problem into
The new binaries are now available here:
http://[insert_favorite_mirror]/dist/jakarta/tomcat-4/v4.1.28-alpha/
(it will not be mirrored until a few hours, so look for it on
www.apache.org for now)
Please test it.
I will post the votes for both 4.1.28 and 5.0.13 early thursday.
Reminder: The TC
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Quick summary:
In o.a.jasper.xmlparserParserUtils.java, line 129 is
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
Does anyone know how DocumentBuilderFactory.newInstance() can throw
java.lang.IllegalStateException: zip file closed?
More detail
On Tue, 07 Oct 2003 13:49:39 +0200
Remy Maucherat [EMAIL PROTECTED] wrote:
There is no guarantee that the binaries d/led are not corrupted on your
random mirror, or haven't been tampered with, or if the mirror is
available at all.
This is for the build process, so mirrors are not a good
35 matches
Mail list logo
