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]



Reply via email to