Re: http bug

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 20 Jan 2010 20:14:07 -0500

Message-ID:

<4b57aa5a$0$275$14726298@news.sunsite.dk>

On 20-01-2010 14:53, Lothar Kimmeringer wrote:

Daniel Pitts wrote:

I often find the standard HttpUrlConnection lacking, and usually go with
apache commons HttpClient instead. You have more control of the
process, if you care, but it also "works" out-of-the-box if you don't
want to configure it as much.

The last time I checked, GetMethod and PostMethod were two
classes sharing a lot of methods but not a common superclass.

Sure?

HttpClient 2.0.2 has a common super class.

So you end up with code like this

if (performGet) {
   methodGet = new GetMethod(host + url);
   methodGet.setQueryString(query);
   methodGet.setDoAuthentication(authNeeded);
   methodGet.getParams().setParameter("http.socket.timeout",
    Integer.valueOf(timeout));
   methodGet.getParams().setParameter(
    HttpMethodParams.RETRY_HANDLER, retryhandler);
   methodGet.setRequestHeader("Connection", "keep-alive");
   methodGet.setRequestHeader("Cache-Control", "no-cache");
}
else {
   methodPost = new PostMethod(host + url);
   methodPost.setRequestHeader("Connection", "keep-alive");
   methodPost.setDoAuthentication(authNeeded);
   methodPost.getParams().setParameter("http.socket.timeout",
    Integer.valueOf(timeout));
   methodPost.getParams().setParameter(
    HttpMethodParams.RETRY_HANDLER, retryhandler);
   methodPost.setRequestHeader("Cache-Control", "no-cache");
}

and so on. If you have a specific HTTP-session to handle
programmatically, HttpClient is nice, but if you have to
build different HTTP-requests in dependence of external
configurations, you have a lot of duplicate code that
is prone to errors.

Most HTTP request receivers are either POST or GET anyway.

I can not imagine sending the exact same data to an URL
just with different method should be that common.

Arne