Making connector defaault address as 0.0.0.0

2006-11-07 Thread Mladen Turk
Hi, With Native connector if the OS supports IPV6 the default address (null) is translated to ::, thus it only listens to the IPV6 addresses. In case the OS doesn't support IPV6 (hardly to be found nowadays), the null address is equivalent to the address=0.0.0.0. The same is for any Java

Re: Making connector defaault address as 0.0.0.0

2006-11-07 Thread Remy Maucherat
Mladen Turk wrote: Hi, With Native connector if the OS supports IPV6 the default address (null) is translated to ::, thus it only listens to the IPV6 addresses. In case the OS doesn't support IPV6 (hardly to be found nowadays), the null address is equivalent to the address=0.0.0.0. The same is

svn commit: r472057 - /tomcat/tc6.0.x/trunk/java/org/apache/jasper/compiler/Validator.java

2006-11-07 Thread remm
Author: remm Date: Tue Nov 7 02:45:01 2006 New Revision: 472057 URL: http://svn.apache.org/viewvc?view=revrev=472057 Log: - 40913: Fix the second test when an expression is used. Modified: tomcat/tc6.0.x/trunk/java/org/apache/jasper/compiler/Validator.java Modified:

Re: Making connector defaault address as 0.0.0.0

2006-11-07 Thread Markus Schönhaber
Mladen Turk wrote: With Native connector if the OS supports IPV6 the default address (null) is translated to ::, thus it only listens to the IPV6 addresses. In case the OS doesn't support IPV6 (hardly to be found nowadays), the null address is equivalent to the address=0.0.0.0. The same is

DO NOT REPLY [Bug 40913] - JasperException raised against valid attribute

2006-11-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40913. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Re: Making connector defaault address as 0.0.0.0

2006-11-07 Thread Mladen Turk
Remy Maucherat wrote: Comments? As you say, 0.0.0.0 is ipv4 so it looks like a bad default value to me, while null means whatever the connector wants. Internally, it's up to the native layer to figure it out, I think. Sure, but the fact is that Java connectors will always use IPV4. APR

DO NOT REPLY [Bug 40911] - problem with request session scope

2006-11-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40911. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Re: New 6.0.x build

2006-11-07 Thread Remy Maucherat
Remy Maucherat wrote: Hi, After all my Jasper fixes (and the other connector fixes), I would like to plan a new 6.0.1 tag for Tuesday. I will also add stuff in the build scripts to prepackage the Maven uploads. Comments ? Ok, so I'll put in a 6.0.1 tag late tonight (let's say 00:00

svn commit: r472087 - /tomcat/tc6.0.x/trunk/webapps/docs/aio.xml

2006-11-07 Thread remm
Author: remm Date: Tue Nov 7 04:41:29 2006 New Revision: 472087 URL: http://svn.apache.org/viewvc?view=revrev=472087 Log: - The page wasn't explicit enough about the requirements, I think. Modified: tomcat/tc6.0.x/trunk/webapps/docs/aio.xml Modified:

Re: Making connector defaault address as 0.0.0.0

2006-11-07 Thread Markus Schönhaber
Mladen Turk wrote: Markus Schönhaber wrote: Mladen Turk wrote: BTW: why is this situation special wrt the native connector? Right, but that's not the case for all supported OS-es. Windows for sure (and Solaris I think) will refuse 127.0.0.1 when the address=:: Do I understand that

DO NOT REPLY [Bug 40906] - java.net.SocketException: Broken pipe from time to time

2006-11-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40906. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

svn commit: r472313 - /tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml

2006-11-07 Thread remm
Author: remm Date: Tue Nov 7 14:43:41 2006 New Revision: 472313 URL: http://svn.apache.org/viewvc?view=revrev=472313 Log: - Changelog update. Modified: tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml Modified: tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml URL:

svn commit: r472328 - /tomcat/tc6.0.x/tags/TOMCAT_6_0_1/

2006-11-07 Thread remm
Author: remm Date: Tue Nov 7 15:34:30 2006 New Revision: 472328 URL: http://svn.apache.org/viewvc?view=revrev=472328 Log: - Tomcat 6.0.1 build. Added: tomcat/tc6.0.x/tags/TOMCAT_6_0_1/ - copied from r472327, tomcat/tc6.0.x/trunk/

DO NOT REPLY [Bug 40911] - problem with request session scope

2006-11-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40911. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Extracting SSL information from servlet

2006-11-07 Thread Andrew Friebel
I hope I have submitted this question via the correct mechanism. I wish to extract certificate information from my servlet that is running within tomcat. The problem that I get is that my x509 certificate array is always null. The code snippet that I am attempting to use is:

Re: New 6.0.x build

2006-11-07 Thread Filip Hanik - Dev Lists
sure, where do you have them, or do you want me to run a build against the tag? Remy Maucherat wrote: Remy Maucherat wrote: Remy Maucherat wrote: Hi, After all my Jasper fixes (and the other connector fixes), I would like to plan a new 6.0.1 tag for Tuesday. I will also add stuff in the