You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by dan tran <da...@gmail.com> on 2004/07/19 18:54:52 UTC
JUnit cookies test failures
Hello, I am running into the same issue found by Eric
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-httpclient-dev@jakarta.apache.org&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: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: JUnit cookies test failures
Posted by dan tran <da...@gmail.com>.
Oleg,
Thank you for a very clear explaination.
-Dan
HttpClient is my pal ;-)
On Tue, 20 Jul 2004 00:22:18 +0200, Oleg Kalnichevski <ol...@apache.org> wrote:
> 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/ReadMsg?listName=commons-httpclient-dev@jakarta.apache.org&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: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: JUnit cookies test failures
Posted by Oleg Kalnichevski <ol...@apache.org>.
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/ReadMsg?listName=commons-httpclient-dev@jakarta.apache.org&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: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org