Dan
It was later discovered that different Tomcat connectors appear to have
different cookie parsing/formating logic. The problem shows up only when
the newer Coyote connector is being used.
<!-- works fine -->
<Connector
className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" />
<!-- applies different cookie paring/formatting rules -->
<!--
<Connector
className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true"/>
-->
However, the real problem is that the TestWebApp based cookie test cases
are completely meaningless as they in fact test Tomcat's functionality
rather than that of HttpClient. In the CVS HEAD (HttpClient 3.0) these
test cases have been removed and replaced with a completely new set of
test cases.
I hope this explains things a little
Oleg
On Mon, 2004-07-19 at 18:54, dan tran wrote:
> Hello, I am running into the same issue found by Eric
>
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1111708
>
> when running against tomcat 4.1.30.
> My tomcat env is on windows XP, httpclient 2.0, jdk 1.4.2
>
> The archive does not seem to have any conclusion yet.
>
> Any suggestion?
>
> -Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
