[5.0] Tester
I have put the tester back in activity for TC 5 (and it caught the failure for error pages), but unfortunately there are a few limitations caused by the HTTP client used (for example, if the status is 500, you can't read the content). It would be a good idea IMO to switch to commons-httpclient (which I'll do, but it's not a very high priority). Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
Is there any chance we'd want to use Latka instead? (Which uses HttpClient) -Tim Remy Maucherat wrote: I have put the tester back in activity for TC 5 (and it caught the failure for error pages), but unfortunately there are a few limitations caused by the HTTP client used (for example, if the status is 500, you can't read the content). It would be a good idea IMO to switch to commons-httpclient (which I'll do, but it's not a very high priority). Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
Tim Funk wrote: Is there any chance we'd want to use Latka instead? (Which uses HttpClient) Well, I don't know that component ;-) There's an apparent problem with it, though: it's an alpha 1 release, and doesn't seem to be evolving anymore (last release in 2001, so it's likely not in sync with HttpClient). Any other ideas ? I think the safest bet would be to adapt the TestClient class to use HttpClient 2.0 b2. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
I don't have much experience using Latka either but it used HttpClient and appeared to use an xml config file for all the tests. It also has the ability to add your own condition classes too. But it does appear dormant in commons. :( +1 to using just HttpClient -Tim Remy Maucherat wrote: Tim Funk wrote: Is there any chance we'd want to use Latka instead? (Which uses HttpClient) Well, I don't know that component ;-) There's an apparent problem with it, though: it's an alpha 1 release, and doesn't seem to be evolving anymore (last release in 2001, so it's likely not in sync with HttpClient). Any other ideas ? I think the safest bet would be to adapt the TestClient class to use HttpClient 2.0 b2. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
What about anteater ? Costin Tim Funk wrote: Is there any chance we'd want to use Latka instead? (Which uses HttpClient) -Tim Remy Maucherat wrote: I have put the tester back in activity for TC 5 (and it caught the failure for error pages), but unfortunately there are a few limitations caused by the HTTP client used (for example, if the status is 500, you can't read the content). It would be a good idea IMO to switch to commons-httpclient (which I'll do, but it's not a very high priority). Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
Costin Manolache wrote: What about anteater ? (yet another project I didn't know about) The sad truth is that I'm lazy :) I want to rewrite the minimum possible amount of code and fix the tests which can't work with the JDK's HTTP client (ex: it returns 500 - TC 5 now restores the original error code; neat - but I still want to read the entity body; the JDK then throws an exception to inform me I'm stupid to attempt to do that; thanks Sun) :) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
On Fri, 18 Jul 2003, Remy Maucherat wrote: Date: Fri, 18 Jul 2003 11:30:35 +0200 From: Remy Maucherat [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: [5.0] Tester I have put the tester back in activity for TC 5 (and it caught the failure for error pages), but unfortunately there are a few limitations caused by the HTTP client used (for example, if the status is 500, you can't read the content). It would be a good idea IMO to switch to commons-httpclient (which I'll do, but it's not a very high priority). Switching is fine if you want, but the existing tester does (or at least it did) have a mode where it uses a low-level socket instead of HttpURLConnection, and therefore doesn't give you the useless garbage on a 500. The trick is to set the protocol property to HTTP/1.0 instead of an empty string. Comments ? Remy Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Tester
Craig R. McClanahan wrote: I have put the tester back in activity for TC 5 (and it caught the failure for error pages), but unfortunately there are a few limitations caused by the HTTP client used (for example, if the status is 500, you can't read the content). It would be a good idea IMO to switch to commons-httpclient (which I'll do, but it's not a very high priority). Switching is fine if you want, but the existing tester does (or at least it did) have a mode where it uses a low-level socket instead of HttpURLConnection, and therefore doesn't give you the useless garbage on a 500. The trick is to set the protocol property to HTTP/1.0 instead of an empty string. I had missed the executeSocket method. That's useful :) Switching to HttpClient still makes sense IMO, but is not essential to fix some tests. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
