Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just wanted to know if any of you had any problems using java default HttpURLConnection class. Some kind of bug that made you switch to apache commons.
Or is it just the (ugly) interface that class exposes that justifies the birth of 3rd party http lib?
Disclosure: I heard some arguments against java.net having some serious problems, but I’m finding hard to believe that a class that is part of the java core distribution still has issues after several releases of the JDK
The things drive me to Apache HttpClient are,
You should use HttpClient 4 (Apache HTTP Components) now.
EDIT: The first problem has been discussed several times here. See,
HttpURLConnection.getResponseCode() returns -1 on second invocation
HttpURLConnection: What's the deal with having to read the whole response?
Even though the problem seems to be worse on Android, we saw the exact problems on J2SE.