From robert49@example.com Sun Feb 01 18:50:25 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 81059 invoked from network); 1 Feb 2009 18:50:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 18:50:24 -0000 Received: (qmail 61460 invoked by uid 500); 1 Feb 2009 18:50:23 -0000 Delivered-To: robert49@example.com Received: (qmail 61374 invoked by uid 500); 1 Feb 2009 18:50:22 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 61315 invoked by uid 99); 1 Feb 2009 18:50:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 10:50:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 18:50:21 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id A9FF3234C4B7 for <robert49@example.com>; Sun, 1 Feb 2009 10:49:59 -0800 (PST) Message-ID: <1574660685.1233514199695.JavaMail.jira@brutus> Date: Sun, 1 Feb 2009 10:49:59 -0800 (PST) From: "Sean Sullivan (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Commented: (HTTPCLIENT-805) Pass ClientConnectionManager to DefaultHttpClient constructor In-Reply-To: <378536257.1224411884261.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCLIENT-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669419#action_12669419 ] Sean Sullivan commented on HTTPCLIENT-805: ------------------------------------------ Are there any plans to resolve this in HttpClient 4.0? (This issue has been open for 3 months and HttpClient 4.0 is still in beta) > Pass ClientConnectionManager to DefaultHttpClient constructor > ------------------------------------------------------------- > > Key: HTTPCLIENT-805 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-805 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpClient, HttpConn > Affects Versions: 4.0 Beta 1 > Reporter: Kenny MacLeod > Fix For: 4.1.0 > > > Copied from my mailing list post, Oleg suggested I post it to JIRA for 4.1 fix. > I'm trying to find the least verbose way of configuring a DefaultHttpClient with a ThreadSafeClientConnManager. > The example code given for this goes through a manual process of configuring HttpParams and SchemeRegistry objects, which is more or less copied from the DefaultHttpClient.createHttpParams() and createClientConnectionManager() methods. > It's a bit of a chicken and egg situation - DefaultHttpClient can create its own HttpParams and SchemeRegistry, which are themselves fine, but only once its been constructed, and the constructor requires the ThreadSafeClientConnManager, but that in turn requires the HttpParams and SchemeRegistry objects. The only way out is to manually construct the HttpParams and SchemeRegistry, which is a waste. > It seems to me that DefaultHttpClient's constructor should take a ClientConnectionManagerFactory instead of a ClientConnectionManager. That way, the createClientConnectionManager() method already has the factory reference, and doesn't have to grub around in the HttpParams object to find it. > The code would then become: > new DefaultHttpClient(new ThreadSafeClientConnManagerFactory(), null); > where ThreadSafeClientConnManagerFactory.newInstance() just constructs ThreadSafeClientConnManager. There's no manual construction of HttpParams and SchemeRegistry, you just leave it up to DefaultHttpClient. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 19:52:21 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 94815 invoked from network); 1 Feb 2009 19:52:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 19:52:21 -0000 Received: (qmail 1650 invoked by uid 500); 1 Feb 2009 19:52:20 -0000 Delivered-To: robert49@example.com Received: (qmail 1620 invoked by uid 500); 1 Feb 2009 19:52:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 1609 invoked by uid 99); 1 Feb 2009 19:52:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 11:52:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 19:52:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id A8C6E234C4B7 for <robert49@example.com>; Sun, 1 Feb 2009 11:51:59 -0800 (PST) Message-ID: <1736183610.1233517919690.JavaMail.jira@brutus> Date: Sun, 1 Feb 2009 11:51:59 -0800 (PST) From: "Oleg Kalnichevski (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Commented: (HTTPCLIENT-805) Pass ClientConnectionManager to DefaultHttpClient constructor In-Reply-To: <378536257.1224411884261.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCLIENT-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669433#action_12669433 ] Oleg Kalnichevski commented on HTTPCLIENT-805: ---------------------------------------------- No, no such plans, unless we are willing to sacrifice complete binary compatibility with the version shipped with Google Android. Oleg > Pass ClientConnectionManager to DefaultHttpClient constructor > ------------------------------------------------------------- > > Key: HTTPCLIENT-805 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-805 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpClient, HttpConn > Affects Versions: 4.0 Beta 1 > Reporter: Kenny MacLeod > Fix For: 4.1.0 > > > Copied from my mailing list post, Oleg suggested I post it to JIRA for 4.1 fix. > I'm trying to find the least verbose way of configuring a DefaultHttpClient with a ThreadSafeClientConnManager. > The example code given for this goes through a manual process of configuring HttpParams and SchemeRegistry objects, which is more or less copied from the DefaultHttpClient.createHttpParams() and createClientConnectionManager() methods. > It's a bit of a chicken and egg situation - DefaultHttpClient can create its own HttpParams and SchemeRegistry, which are themselves fine, but only once its been constructed, and the constructor requires the ThreadSafeClientConnManager, but that in turn requires the HttpParams and SchemeRegistry objects. The only way out is to manually construct the HttpParams and SchemeRegistry, which is a waste. > It seems to me that DefaultHttpClient's constructor should take a ClientConnectionManagerFactory instead of a ClientConnectionManager. That way, the createClientConnectionManager() method already has the factory reference, and doesn't have to grub around in the HttpParams object to find it. > The code would then become: > new DefaultHttpClient(new ThreadSafeClientConnManagerFactory(), null); > where ThreadSafeClientConnManagerFactory.newInstance() just constructs ThreadSafeClientConnManager. There's no manual construction of HttpParams and SchemeRegistry, you just leave it up to DefaultHttpClient. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 20:02:44 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 95722 invoked from network); 1 Feb 2009 20:02:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 20:02:44 -0000 Received: (qmail 3649 invoked by uid 500); 1 Feb 2009 20:02:43 -0000 Delivered-To: robert49@example.com Received: (qmail 3614 invoked by uid 500); 1 Feb 2009 20:02:43 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 3593 invoked by uid 99); 1 Feb 2009 20:02:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 12:02:42 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO ok2consulting.nine.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 20:02:35 +0000 Received: by ok2consulting.nine.ch (Postfix, from userid 1002) id 09259198568; Sun, 1 Feb 2009 21:02:12 +0100 (CET) Received: from [83.161.120.155] (448)341-0601.dclient.hispeed.ch [83.161.120.155]) by ok2consulting.nine.ch (Postfix) with ESMTP id 12EFC198523; Sun, 1 Feb 2009 21:02:09 +0100 (CET) Message-ID: <robert49@example.com> Date: Sun, 01 Feb 2009 21:01:58 +0100 From: Oleg Kalnichevski <robert49@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20081209) MIME-Version: 1.0 To: robert49@example.com, robert49@example.com Subject: [HttpCore] HttpCore 4.0 final release is imminent Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on ok2consulting.nine.ch X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.3 Folks I have finally completed documentation for HttpCore. You can find the preview of API docs here: http://people.apache.org/~olegk/httpcore-4.0-final/doc/site/apidocs/ The HttpCore tutorial can be found here: [html] http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/html/ [pdf] http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/pdf/index.pdf There have been virtually no major bugs found in HttpCore since the last release. We have had only two bug fixes in the past 4 months. I personally think there no longer any reason delaying the final release, especially given the fact there is now a complete API documentation. Please review the documents and let me know what you think. Please feel free to point out areas that need more coverage. Any feedback, comment, or critique will be hugely appreciated. If I hear no major complaints about the quality of documentation I will start cutting the official release packages approximately in a week time. The same work needs to be done for HttpClient 4.0 at some point of time. The sooner the documentation for HttpClient is completed the sooner we can release the final 4.0 version. So, a helping hand would be very, very, very appreciated. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 22:52:21 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 46539 invoked from network); 1 Feb 2009 22:52:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 22:52:21 -0000 Received: (qmail 32285 invoked by uid 500); 1 Feb 2009 22:52:21 -0000 Delivered-To: robert49@example.com Received: (qmail 32076 invoked by uid 500); 1 Feb 2009 22:52:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 32065 invoked by uid 99); 1 Feb 2009 22:52:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 14:52:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 22:52:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 955DA234C4AC for <robert49@example.com>; Sun, 1 Feb 2009 14:51:59 -0800 (PST) Message-ID: <1398599814.1233528719610.JavaMail.jira@brutus> Date: Sun, 1 Feb 2009 14:51:59 -0800 (PST) From: "James Abley (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Commented: (HTTPCLIENT-816) HttClient should support Accept-Encoding: gzip out of the box In-Reply-To: <1160503195.1232413259665.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCLIENT-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669473#action_12669473 ] James Abley commented on HTTPCLIENT-816: ---------------------------------------- No need to take things personally, I was implying that HttpClient is failing if it doesn't do that out of the box. Let's examine why I would make that claim: 1. HttpClient should encapsulate the details of RFC2616 such that most end users don't need to worry about it. 'The machine should deal with the details'. RFC2616 is in my top 3 RFCs, but I wouldn't say I'm a typical end-user of HttpClient. 2.. Support in other languages - Python httplib2. >>> import httplib2 >>> response, content = http.request('http://www.apache.org/') Using Wireshark, I can see that the request is made and supports compress and gzip encodings without the client developer having to know RFC2616 intimately or worry about handling the low level details like that. GET / HTTP/1.1\r\n Host: www.apache.org\r\n accept-encoding: compress, gzip\r\n user-agent: Python-httplib2/$Rev: 259 $\r\n As an aside, httplib2 also has great in-built cache support and understands ETag / Last-Modified to transparently do conditional GET when required, but that's another discussion. 3. Only do gzip support - I personally have encountered problematic deflate in the wild, and it is a fairly well-known issue; see <http://groups.google.com/group/comp.compression/msg/e6bbe67658d97d96?hl=en> Compress isn't widely used AFAIK; in fact I've never seen it. Identity is obviously a no-op. I'll raise it on the developers list as well. Cheers, James > HttClient should support Accept-Encoding: gzip out of the box > ------------------------------------------------------------- > > Key: HTTPCLIENT-816 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-816 > Project: HttpComponents HttpClient > Issue Type: New Feature > Components: HttpClient > Affects Versions: 3.1.1 > Environment: Any > Reporter: James Abley > Priority: Minor > Attachments: accept-encoding.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > I think HttpClient really ought to support Accept-Encoding: gzip without requiring any effort from the client developer. Allowing Content-Encoding: gzip responses can be a great bandwidth saver. > But it also needs to cater for developers that have coded their own solution to this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 23:10:23 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 52059 invoked from network); 1 Feb 2009 23:10:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 23:10:23 -0000 Received: (qmail 60127 invoked by uid 500); 1 Feb 2009 23:10:22 -0000 Delivered-To: robert49@example.com Received: (qmail 60086 invoked by uid 500); 1 Feb 2009 23:10:22 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 60075 invoked by uid 99); 1 Feb 2009 23:10:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 15:10:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 23:10:20 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 9ACFD234C4AC for <robert49@example.com>; Sun, 1 Feb 2009 15:09:59 -0800 (PST) Message-ID: <633829157.1233529799633.JavaMail.jira@brutus> Date: Sun, 1 Feb 2009 15:09:59 -0800 (PST) From: "Oleg Kalnichevski (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Commented: (HTTPCLIENT-816) HttClient should support Accept-Encoding: gzip out of the box In-Reply-To: <1160503195.1232413259665.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCLIENT-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669476#action_12669476 ] Oleg Kalnichevski commented on HTTPCLIENT-816: ---------------------------------------------- HttpClient is _not_ a browser. It is an HTTP transport library. It is irrelevant what present generation of browsers can or cannot do. We should either provide a reasonably complete support for content encodings as defined in RFC2616, or leave GZip compression as an option available from the 'contrib' package. Oleg > HttClient should support Accept-Encoding: gzip out of the box > ------------------------------------------------------------- > > Key: HTTPCLIENT-816 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-816 > Project: HttpComponents HttpClient > Issue Type: New Feature > Components: HttpClient > Affects Versions: 3.1.1 > Environment: Any > Reporter: James Abley > Priority: Minor > Attachments: accept-encoding.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > I think HttpClient really ought to support Accept-Encoding: gzip without requiring any effort from the client developer. Allowing Content-Encoding: gzip responses can be a great bandwidth saver. > But it also needs to cater for developers that have coded their own solution to this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 23:18:24 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 52865 invoked from network); 1 Feb 2009 23:18:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 23:18:22 -0000 Received: (qmail 67073 invoked by uid 500); 1 Feb 2009 23:18:22 -0000 Delivered-To: robert49@example.com Received: (qmail 67034 invoked by uid 500); 1 Feb 2009 23:18:21 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 67023 invoked by uid 99); 1 Feb 2009 23:18:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 15:18:21 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 23:18:21 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id F0BFE234C4B7 for <robert49@example.com>; Sun, 1 Feb 2009 15:18:00 -0800 (PST) Message-ID: <1191132536.1233530280984.JavaMail.jira@brutus> Date: Sun, 1 Feb 2009 15:18:00 -0800 (PST) From: "Sebb (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Created: (HTTPCLIENT-821) HttpConnection.shutdown() not always thread-safe MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org HttpConnection.shutdown() not always thread-safe ------------------------------------------------ Key: HTTPCLIENT-821 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-821 Project: HttpComponents HttpClient Issue Type: Bug Reporter: Sebb Fix For: 4.0 Final The documentation says that the HttpConnection is generally not thread-safe, but that the shutdown() method is thread-safe. However this is not the case at present for the methods: org.apache.http.impl.SocketHttpClientConnection.shutdown() org.apache.http.impl.SocketHttpServerConnection.shutdown() It reads the socket from the instance variable "this.socket" which is not synchronised, final or volatile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Sun Feb 01 23:35:13 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 54426 invoked from network); 1 Feb 2009 23:35:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2009 23:35:13 -0000 Received: (qmail 71210 invoked by uid 500); 1 Feb 2009 23:35:13 -0000 Delivered-To: robert49@example.com Received: (qmail 71172 invoked by uid 500); 1 Feb 2009 23:35:13 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 71160 invoked by uid 99); 1 Feb 2009 23:35:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 15:35:13 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robert49@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-ew0-f21.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 23:35:06 +0000 Received: by ewy14 with SMTP id 14so1593719ewy.22 for <robert49@example.com>; Sun, 01 Feb 2009 15:34:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=0DtkWlFsGJcJ99I+C0TE7Aiqm43ykyWfOMEKMLgxS+o=; b=BqVkubObzj5coI21jq7AH/9sIhxwuez3w5jEYBt/a5+F/wQt5BrpXC57zBjNvkCrhk 9wFB1LqAowsK8+R1cPKIu/2btVj04i2vISejeFKoUzUDgUlP8JC1s03lphJViuF9AwZ2 H68ofz0ApV9QB1xR5hBdVlh1j0Hwl1L7nd47A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=OZsitCncCmZFxQ0SgNvjb/EJDO7R3ggkOLyM9p/7Ryw8MMNU5PPKq8WisZ0cye5BRs k08xMMK8FkEp2jNmyt3LaLfXv9sH2UmV+24iB5oaeo6UHtDZpnOwHYCwmp0V+vzAkPRc x9qUpBjJXT/eGxZRXKslTVkiNXx48ynZuDNIQ= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id y4mr1589927eba.23.1233531284959; Sun, 01 Feb 2009 15:34:44 -0800 (PST) Date: Sun, 1 Feb 2009 23:34:44 +0000 Message-ID: <robert49@example.com> Subject: BasicHttpRequest not thread-safe but can be easily made so From: sebb <robert49@example.com> To: HttpComponents Project <robert49@example.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org BasicHttpRequest currently has a non-final field "requestLine". This could be made final, and the check/update of the field in getRequestLine() removed, as the field cannot be null. S/// --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 00:03:54 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 66193 invoked from network); 2 Feb 2009 00:03:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 00:03:54 -0000 Received: (qmail 6781 invoked by uid 500); 2 Feb 2009 00:03:53 -0000 Delivered-To: robert49@example.com Received: (qmail 6750 invoked by uid 500); 2 Feb 2009 00:03:53 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 6739 invoked by uid 99); 2 Feb 2009 00:03:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Feb 2009 16:03:53 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robert49@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ey-out-1920.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 00:03:47 +0000 Received: by ey-out-1920.google.com with SMTP id 13so141695eye.10 for <robert49@example.com>; Sun, 01 Feb 2009 16:03:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=DpcxQKbeTy8dToMEu4DfC+DGgeNWlLrO9iFLmriWJHQ=; b=lAYPqSkBWRCOMyVrU8GSsX2ymL2zrRP3UhO6nBIE2mGcy6+MeW4xtopmOaDDUqE/dt NjYtMEa1FwJyMUWJ4TI6SxPl34duwHyxwNNJglTdCnUSM1oapWaTnjT/Kof1oQx+OP4v YE6nd3XcQ9ky+gEJhEZZeiMhRvVJXdbV6Bw5A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=GOL4u9I9EAHATdWmeNsJY5MeOwtu7VNZkN/dczPwkAkKGs0icWnf6pzYpbbAH6V3ty NXOkqiI7ZUqnhPknJO2Dk9cDJm5gJRDxf8tBDThibRBtemE2FgPAGwpI7hbEkoYiGh3t 85OZPeN+9ACedz3U/8qEzK4hBcfFjt8XzFbbE= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id o17mr4069590ebd.195.1233533005511; Sun, 01 Feb 2009 16:03:25 -0800 (PST) In-Reply-To: <robert49@example.com> References: <robert49@example.com> Date: Mon, 2 Feb 2009 00:03:25 +0000 Message-ID: <robert49@example.com> Subject: Re: [HttpCore] HttpCore 4.0 final release is imminent From: sebb <robert49@example.com> To: HttpComponents Project <robert49@example.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 01/02/2009, Oleg Kalnichevski <robert49@example.com> wrote: > Folks > > I have finally completed documentation for HttpCore. You can find the > preview of API docs here: > > http://people.apache.org/~olegk/httpcore-4.0-final/doc/site/apidocs/ > > The HttpCore tutorial can be found here: > > [html] > http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/html/ > [pdf] > http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/pdf/index.pdf The documentation is very impressive. Very clear and appears to cover pretty well everything. It's particularly helpful that it documents which methods and classes are intended to be thread-safe. > There have been virtually no major bugs found in HttpCore since the last > release. We have had only two bug fixes in the past 4 months. I personally > think there no longer any reason delaying the final release, especially > given the fact there is now a complete API documentation. > > Please review the documents and let me know what you think. Please feel > free to point out areas that need more coverage. Any feedback, comment, or > critique will be hugely appreciated. If I hear no major complaints about the > quality of documentation I will start cutting the official release packages > approximately in a week time. I think there are some problems with the thread-safety of certain classes. I have raised a JIRA for one such - and an e-mail for another, but it seems to me that this needs robert49@example.com. The main problems are instance variables that are shared between threads - unless these are final, volatile or synchronised, there is no guarantee that what one thread writes to a field will ever be seen by another thread. Or, maybe the other thread will see an updated object reference but the object itself may be incompletely updated. Some such problems may be easy to fix; others may not... > The same work needs to be done for HttpClient 4.0 at some point of time. > The sooner the documentation for HttpClient is completed the sooner we can > release the final 4.0 version. So, a helping hand would be very, very, very > appreciated. Sorry for the late stage at which this is raised - I've been meaning to look at thread-safety for some time, but I was not entirely sure which classes/methods were intended to be thread-safe. > Oleg > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: robert49@example.com > For additional commands, e-mail: robert49@example.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 12:06:28 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 21530 invoked from network); 2 Feb 2009 12:06:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 12:06:22 -0000 Received: (qmail 41578 invoked by uid 500); 2 Feb 2009 12:06:21 -0000 Delivered-To: robert49@example.com Received: (qmail 41484 invoked by uid 500); 2 Feb 2009 12:06:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 41432 invoked by uid 99); 2 Feb 2009 12:06:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 04:06:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 12:06:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 9886A234C4BD for <robert49@example.com>; Mon, 2 Feb 2009 04:05:59 -0800 (PST) Message-ID: <269707560.1233576359623.JavaMail.jira@brutus> Date: Mon, 2 Feb 2009 04:05:59 -0800 (PST) From: =?utf-8?Q?Joan_Balaguer=C3=B3_=28JIRA=29?= <robert49@example.com> To: robert49@example.com Subject: [jira] Created: (HTTPCLIENT-822) HttpClient throws java.net.SocketException instead of org.apache.http.conn.ConnectionTimeoutException when connection timeout occurs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org HttpClient throws java.net.SocketException instead of org.apache.http.conn.= ConnectionTimeoutException when connection timeout occurs ---------------------------------------------------------------------------= --------------------------------------------------------- Key: HTTPCLIENT-822 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-822 Project: HttpComponents HttpClient Issue Type: Bug Components: HttpClient, HttpConn Affects Versions: 4.0 Beta 2 Reporter: Joan Balaguer=C3=B3 Fix For: 4.0 Beta 3 When sending an http request a connection timeout occurs, the HttpClient.ex= ecute method throws a java.net.SocketException instead of a org.apache.http= .conn.ConnectionTimeoutException. java.net.SocketTimeoutException: connect timed robert49@example.com(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:1= 95) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(Pla= inSocketFactory.java:119) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openCo= nnection(DefaultClientConnectionOperator.java:129) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEnt= ry.java:164) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(Abstrac= tPooledConnAdapter.java:119) at org.apache.http.impl.client.DefaultRequestDirector.execute(Defau= ltRequestDirector.java:349) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractH= ttpClient.java:555) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractH= ttpClient.java:487) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractH= ttpClient.java:465) --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 16:40:28 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 55792 invoked from network); 2 Feb 2009 16:40:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 16:40:28 -0000 Received: (qmail 38992 invoked by uid 500); 2 Feb 2009 16:40:27 -0000 Delivered-To: robert49@example.com Received: (qmail 38969 invoked by uid 500); 2 Feb 2009 16:40:27 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 38958 invoked by uid 99); 2 Feb 2009 16:40:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 08:40:27 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO smtp02.msg.oleane.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 16:40:18 +0000 Received: from JBoss-JSDA-dev.ac-consulting.fr ([83.161.120.155]) (authenticated) by smtp02.msg.oleane.net (MTA) with ESMTP id n12GdaWp016530 for <robert49@example.com>; Mon, 2 Feb 2009 17:39:36 +0100 X-DKIM: Sendmail DKIM Filter v2.8.1 smtp02.msg.oleane.net n12GdaWp016530 Authentication-Results: smtp02.msg.oleane.net; dkim=none (no signature) header.i=unknown; dkim-adsp=none X-Oleane-Rep: REPA Message-Id: <robert49@example.com> From: Patrick JUSSEAU <robert49@example.com> To: robert49@example.com Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Newbie troubles.... Date: Mon, 2 Feb 2009 17:39:36 +0100 X-Mailer: Apple Mail (2.930.3) X-PMX-Spam: Probability=8% X-PFSI-Info: PMX 83.161.120.1556843, Antispam-Engine: 83.161.120.1550677, Antispam-Data: 283.161.120.155529 (no antivirus check) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: NO Hi all, I am pretty new to the http components world but I need to use it for a simple case I need to deal with. What I need to do is : 1 - send a request using https to a remote server with a POST method 2- pass parameters to this request (key/value pairs) 3 - get a response back and read the response parameters I tried to read through the examples but I can't find an easy way to do this, I feel a little bit lost in the API. Could anyone point me to the right direction? Many thanks!! Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 17:16:41 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 73327 invoked from network); 2 Feb 2009 17:16:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 17:16:41 -0000 Received: (qmail 11238 invoked by uid 500); 2 Feb 2009 17:16:41 -0000 Delivered-To: robert49@example.com Received: (qmail 11032 invoked by uid 500); 2 Feb 2009 17:16:40 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 11021 invoked by uid 99); 2 Feb 2009 17:16:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 09:16:40 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: unknown ipv4:83.161.120.155/27 (nike.apache.org: encountered unrecognized mechanism during SPF processing of domain of robert49@example.com) Received: from [83.161.120.155] (HELO viefep15-int.chello.at) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 17:16:30 +0000 Received: from edge03.upc.biz ([83.161.120.155]) by viefep15-int.chello.at (InterMail vM.83.161.120.155 201-2219-108-20080618) with ESMTP id <robert49@example.com> for <robert49@example.com>; Mon, 2 Feb 2009 18:16:09 +0100 Received: from gollum.odi.ch ([83.161.120.155]) by edge03.upc.biz with edge id B5G61b02t1Jb14D035G7TF; Mon, 02 Feb 2009 18:16:09 +0100 X-SourceIP: 83.161.120.155 Received: from [83.161.120.155] (cvs.logobject.ch [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gollum.odi.ch (Postfix) with ESMTPSA id 597D5110BC for <robert49@example.com>; Mon, 2 Feb 2009 18:16:06 +0100 (CET) Message-ID: <robert49@example.com> Date: Mon, 02 Feb 2009 18:16:04 +0100 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= <robert49@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20081209) MIME-Version: 1.0 To: HttpComponents Project <robert49@example.com> Subject: Re: Newbie troubles.... References: <robert49@example.com> In-Reply-To: <robert49@example.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Patrick, Please see http://hc.apache.org/httpcomponents-client/examples.html There is examples for all your questions: 1. see Custom SSL context, see SSLSocketFactory 2. see Form based logon, see UrlEncodedFormEntity 3. Response handling, see HttpResponse, see ResponseHandler and HttpClient.execute(HttpUriRequest, ResponseHandler) Also visit the API Doc: http://hc.apache.org/httpcomponents-client/httpclient/apidocs/index.html Cheers, Ortwin Patrick JUSSEAU wrote: > Hi all, > > I am pretty new to the http components world but I need to use it for a > simple case I need to deal with. What I need to do is : > > > 1 - send a request using https to a remote server with a POST method > 2- pass parameters to this request (key/value pairs) > 3 - get a response back and read the response parameters > > I tried to read through the examples but I can't find an easy way to do > this, I feel a little bit lost in the API. Could anyone point me to the > right direction? > > Many thanks!! > > > Patrick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: robert49@example.com > For additional commands, e-mail: robert49@example.com > -- [web] http://www.odi.ch/ [blog] http://www.odi.ch/weblog/ [pgp] key 0x81CF3416 finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 18:48:21 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 24444 invoked from network); 2 Feb 2009 18:48:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 18:48:21 -0000 Received: (qmail 54786 invoked by uid 500); 2 Feb 2009 18:48:20 -0000 Delivered-To: robert49@example.com Received: (qmail 54745 invoked by uid 500); 2 Feb 2009 18:48:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 54728 invoked by uid 99); 2 Feb 2009 18:48:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 10:48:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 18:48:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D8582234C4AA for <robert49@example.com>; Mon, 2 Feb 2009 10:47:59 -0800 (PST) Message-ID: <559617634.1233600479884.JavaMail.jira@brutus> Date: Mon, 2 Feb 2009 10:47:59 -0800 (PST) From: "Oleg Kalnichevski (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Moved: (HTTPCORE-182) HttpConnection.shutdown() not always thread-safe In-Reply-To: <1191132536.1233530280984.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCORE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski moved HTTPCLIENT-821 to HTTPCORE-182: ------------------------------------------------------- Fix Version/s: (was: 4.0 Final) 4.0-beta4 Key: HTTPCORE-182 (was: HTTPCLIENT-821) Project: HttpComponents HttpCore (was: HttpComponents HttpClient) > HttpConnection.shutdown() not always thread-safe > ------------------------------------------------ > > Key: HTTPCORE-182 > URL: https://issues.apache.org/jira/browse/HTTPCORE-182 > Project: HttpComponents HttpCore > Issue Type: Bug > Reporter: Sebb > Fix For: 4.0-beta4 > > > The documentation says that the HttpConnection is generally not thread-safe, but that the shutdown() method is thread-safe. > However this is not the case at present for the methods: > org.apache.http.impl.SocketHttpClientConnection.shutdown() > org.apache.http.impl.SocketHttpServerConnection.shutdown() > It reads the socket from the instance variable "this.socket" which is not synchronised, final or volatile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 18:50:21 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 24969 invoked from network); 2 Feb 2009 18:50:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 18:50:21 -0000 Received: (qmail 59447 invoked by uid 500); 2 Feb 2009 18:50:20 -0000 Delivered-To: robert49@example.com Received: (qmail 59414 invoked by uid 500); 2 Feb 2009 18:50:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 59403 invoked by uid 99); 2 Feb 2009 18:50:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 10:50:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 18:50:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id BB117234C4AA for <robert49@example.com>; Mon, 2 Feb 2009 10:49:59 -0800 (PST) Message-ID: <1538673701.1233600599765.JavaMail.jira@brutus> Date: Mon, 2 Feb 2009 10:49:59 -0800 (PST) From: "Oleg Kalnichevski (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Resolved: (HTTPCORE-182) HttpConnection.shutdown() not always thread-safe In-Reply-To: <1191132536.1233530280984.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCORE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski resolved HTTPCORE-182. ---------------------------------------- Resolution: Fixed Made variables volatile. This should fix the issue. Please review. Oleg > HttpConnection.shutdown() not always thread-safe > ------------------------------------------------ > > Key: HTTPCORE-182 > URL: https://issues.apache.org/jira/browse/HTTPCORE-182 > Project: HttpComponents HttpCore > Issue Type: Bug > Reporter: Sebb > Fix For: 4.0-beta4 > > > The documentation says that the HttpConnection is generally not thread-safe, but that the shutdown() method is thread-safe. > However this is not the case at present for the methods: > org.apache.http.impl.SocketHttpClientConnection.shutdown() > org.apache.http.impl.SocketHttpServerConnection.shutdown() > It reads the socket from the instance variable "this.socket" which is not synchronised, final or volatile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 18:58:33 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 26333 invoked from network); 2 Feb 2009 18:58:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 18:58:32 -0000 Received: (qmail 71252 invoked by uid 500); 2 Feb 2009 18:58:32 -0000 Delivered-To: robert49@example.com Received: (qmail 71228 invoked by uid 500); 2 Feb 2009 18:58:31 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 71209 invoked by uid 99); 2 Feb 2009 18:58:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 10:58:31 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO smtp06.msg.oleane.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 18:58:22 +0000 Received: from JBoss-JSDA-dev.ac-consulting.fr ([83.161.120.155]) (authenticated) by smtp06.msg.oleane.net (MTA) with ESMTP id n12IYoGV012631 for <robert49@example.com>; Mon, 2 Feb 2009 19:34:50 +0100 X-DKIM: Sendmail DKIM Filter v2.8.1 smtp06.msg.oleane.net n12IYoGV012631 Authentication-Results: smtp06.msg.oleane.net; dkim=none (no signature) header.i=unknown; dkim-adsp=none X-Oleane-Rep: REPA Message-Id: <robert49@example.com> From: Patrick JUSSEAU <robert49@example.com> To: "HttpComponents Project" <robert49@example.com> In-Reply-To: <robert49@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Newbie troubles.... Date: Mon, 2 Feb 2009 19:34:50 +0100 References: <robert49@example.com> <robert49@example.com> X-Mailer: Apple Mail (2.930.3) X-PMX-Spam: Probability=8% X-PFSI-Info: PMX 83.161.120.1556843, Antispam-Engine: 83.161.120.1550677, Antispam-Data: 283.161.120.155621 (no antivirus check) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: NO Thanks Ortwin for the pointers, I see clearly now. I am able to send =20 my post request and get a response back from the https server. I was =20 however wondering if there is a utility class that parses the =20 HttpEntity response content in order to get key value pairs (the =20 content of the response entity is key1=3Dvalue1&key2=3Dvalue2&...) ? Something that would look like : HttpEntity resEntity =3D response.getEntity(); List<NameValuePair> nvps =3D SomeUtilityClass.getNameValuePairs(); If such a class does not exist does it mean I need to parse it myself? Thanks, Patrick On 2 f=E9vr. 09, at 18:16, Ortwin Gl=FCck wrote: > Patrick, > > Please see http://hc.apache.org/httpcomponents-client/examples.html > There is examples for all your questions: > > 1. see Custom SSL context, see SSLSocketFactory > 2. see Form based logon, see UrlEncodedFormEntity > 3. Response handling, see HttpResponse, see ResponseHandler and > HttpClient.execute(HttpUriRequest, ResponseHandler) > > Also visit the API Doc: > = http://hc.apache.org/httpcomponents-client/httpclient/apidocs/index.html > > Cheers, > > Ortwin > > Patrick JUSSEAU wrote: >> Hi all, >> >> I am pretty new to the http components world but I need to use it =20 >> for a >> simple case I need to deal with. What I need to do is : >> >> >> 1 - send a request using https to a remote server with a POST method >> 2- pass parameters to this request (key/value pairs) >> 3 - get a response back and read the response parameters >> >> I tried to read through the examples but I can't find an easy way =20 >> to do >> this, I feel a little bit lost in the API. Could anyone point me to =20= >> the >> right direction? >> >> Many thanks!! >> >> >> Patrick >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: robert49@example.com >> For additional commands, e-mail: robert49@example.com >> > > --=20 > [web] http://www.odi.ch/ > [blog] http://www.odi.ch/weblog/ > [pgp] key 0x81CF3416 > finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: robert49@example.com > For additional commands, e-mail: robert49@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 19:02:02 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 26960 invoked from network); 2 Feb 2009 19:02:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 19:02:02 -0000 Received: (qmail 72237 invoked by uid 500); 2 Feb 2009 19:02:02 -0000 Delivered-To: robert49@example.com Received: (qmail 72195 invoked by uid 500); 2 Feb 2009 19:02:02 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 72184 invoked by uid 99); 2 Feb 2009 19:02:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 11:02:01 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO ok2consulting.nine.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 19:01:52 +0000 Received: by ok2consulting.nine.ch (Postfix, from userid 1002) id BB2C0198523; Mon, 2 Feb 2009 20:01:31 +0100 (CET) Received: from [83.161.120.155] (448)341-0601.dclient.hispeed.ch [83.161.120.155]) by ok2consulting.nine.ch (Postfix) with ESMTP id 9A45F198523 for <robert49@example.com>; Mon, 2 Feb 2009 20:01:25 +0100 (CET) Message-ID: <robert49@example.com> Date: Mon, 02 Feb 2009 20:01:24 +0100 From: Oleg Kalnichevski <robert49@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20081209) MIME-Version: 1.0 To: HttpComponents Project <robert49@example.com> Subject: Re: BasicHttpRequest not thread-safe but can be easily made so References: <robert49@example.com> In-Reply-To: <robert49@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on ok2consulting.nine.ch X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.3 sebb wrote: > BasicHttpRequest currently has a non-final field "requestLine". > > This could be made final, and the check/update of the field in > getRequestLine() removed, as the field cannot be null. > > S/// > Hi Sebastian, The reason for this variable being non-final is to make it possible to mutate HTTP protocol version of an existing BasicHttpRequest through the HttpParams collection associated with the object. It is basically a hangover from the 3.x days. I do not mind changing the behavior and making the variable final. Oleg > --------------------------------------------------------------------- > To unsubscribe, e-mail: robert49@example.com > For additional commands, e-mail: robert49@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 19:09:51 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 28633 invoked from network); 2 Feb 2009 19:09:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 19:09:51 -0000 Received: (qmail 83846 invoked by uid 500); 2 Feb 2009 19:09:51 -0000 Delivered-To: robert49@example.com Received: (qmail 83810 invoked by uid 500); 2 Feb 2009 19:09:51 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 83799 invoked by uid 99); 2 Feb 2009 19:09:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 11:09:51 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO ok2consulting.nine.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 19:09:43 +0000 Received: by ok2consulting.nine.ch (Postfix, from userid 1002) id E7071198568; Mon, 2 Feb 2009 20:09:20 +0100 (CET) Received: from [83.161.120.155] (448)341-0601.dclient.hispeed.ch [83.161.120.155]) by ok2consulting.nine.ch (Postfix) with ESMTP id 6E809198523 for <robert49@example.com>; Mon, 2 Feb 2009 20:09:04 +0100 (CET) Message-ID: <robert49@example.com> Date: Mon, 02 Feb 2009 20:09:03 +0100 From: Oleg Kalnichevski <robert49@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20081209) MIME-Version: 1.0 To: HttpComponents Project <robert49@example.com> Subject: Re: [HttpCore] HttpCore 4.0 final release is imminent References: <robert49@example.com> <robert49@example.com> In-Reply-To: <robert49@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on ok2consulting.nine.ch X-Spam-Level: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.3 sebb wrote: > On 01/02/2009, Oleg Kalnichevski <robert49@example.com> wrote: >> Folks >> >> I have finally completed documentation for HttpCore. You can find the >> preview of API docs here: >> >> http://people.apache.org/~olegk/httpcore-4.0-final/doc/site/apidocs/ >> >> The HttpCore tutorial can be found here: >> >> [html] >> http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/html/ >> [pdf] >> http://people.apache.org/~olegk/httpcore-4.0-final/doc/docbkx/pdf/index.pdf > > The documentation is very impressive. Very clear and appears to cover > pretty well everything. > > It's particularly helpful that it documents which methods and classes > are intended to be thread-safe. > >> There have been virtually no major bugs found in HttpCore since the last >> release. We have had only two bug fixes in the past 4 months. I personally >> think there no longer any reason delaying the final release, especially >> given the fact there is now a complete API documentation. >> >> Please review the documents and let me know what you think. Please feel >> free to point out areas that need more coverage. Any feedback, comment, or >> critique will be hugely appreciated. If I hear no major complaints about the >> quality of documentation I will start cutting the official release packages >> approximately in a week time. > > I think there are some problems with the thread-safety of certain classes. > I have raised a JIRA for one such - and an e-mail for another, but it > seems to me that this needs robert49@example.com. > > The main problems are instance variables that are shared between > threads - unless these are final, volatile or synchronised, there is > no guarantee that what one thread writes to a field will ever be seen > by another thread. Or, maybe the other thread will see an updated > object reference but the object itself may be incompletely updated. > > Some such problems may be easy to fix; others may not... > Sebastian, Just let me know what needs to be looked at or just go ahead and fix it yourself. We certainly should not release 4.0 final as long as there are known potential concurrency issues. Cheers Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 19:47:55 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 36777 invoked from network); 2 Feb 2009 19:47:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 19:47:55 -0000 Received: (qmail 20023 invoked by uid 500); 2 Feb 2009 19:47:54 -0000 Delivered-To: robert49@example.com Received: (qmail 19995 invoked by uid 500); 2 Feb 2009 19:47:54 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 19984 invoked by uid 99); 2 Feb 2009 19:47:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 11:47:54 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: unknown ipv4:83.161.120.155/27 (nike.apache.org: encountered unrecognized mechanism during SPF processing of domain of robert49@example.com) Received: from [83.161.120.155] (HELO viefep17-int.chello.at) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 19:47:42 +0000 Received: from edge03.upc.biz ([83.161.120.155]) by viefep17-int.chello.at (InterMail vM.83.161.120.155 201-2219-108-20080618) with ESMTP id <robert49@example.com> for <robert49@example.com>; Mon, 2 Feb 2009 20:47:21 +0100 Received: from gollum.odi.ch ([83.161.120.155]) by edge03.upc.biz with edge id B7nJ1b0221Jb14D037nKaY; Mon, 02 Feb 2009 20:47:21 +0100 X-SourceIP: 83.161.120.155 Received: from [83.161.120.155] (mithril [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gollum.odi.ch (Postfix) with ESMTPSA id 5EFD11042A for <robert49@example.com>; Mon, 2 Feb 2009 20:47:18 +0100 (CET) Message-ID: <robert49@example.com> Date: Mon, 02 Feb 2009 20:47:18 +0100 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= <robert49@example.com> User-Agent: Thunderbird 83.161.120.155 (X11/20090102) MIME-Version: 1.0 To: HttpComponents Project <robert49@example.com> Subject: Re: Newbie troubles.... References: <robert49@example.com> <robert49@example.com> <robert49@example.com> In-Reply-To: <robert49@example.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Patrick, That's not really a standard for a response. So naturally we have no such parser. It's however easy to parse: 1. split by the & character using StringTokenizer 2. split each pair by the = character using String.indexOf 3. decode each name and value with URIDecoder Cheers, Ortwin Patrick JUSSEAU wrote: > Thanks Ortwin for the pointers, I see clearly now. I am able to send my > post request and get a response back from the https server. I was > however wondering if there is a utility class that parses the HttpEntity > response content in order to get key value pairs (the content of the > response entity is key1=value1&key2=value2&...) ? > > Something that would look like : > > HttpEntity resEntity = response.getEntity(); > List<NameValuePair> nvps = SomeUtilityClass.getNameValuePairs(); > > If such a class does not exist does it mean I need to parse it myself? > > Thanks, > > Patrick > > On 2 févr. 09, at 18:16, Ortwin Glück wrote: > >> Patrick, >> >> Please see http://hc.apache.org/httpcomponents-client/examples.html >> There is examples for all your questions: >> >> 1. see Custom SSL context, see SSLSocketFactory >> 2. see Form based logon, see UrlEncodedFormEntity >> 3. Response handling, see HttpResponse, see ResponseHandler and >> HttpClient.execute(HttpUriRequest, ResponseHandler) >> >> Also visit the API Doc: >> http://hc.apache.org/httpcomponents-client/httpclient/apidocs/index.html >> >> Cheers, >> >> Ortwin >> >> Patrick JUSSEAU wrote: >>> Hi all, >>> >>> I am pretty new to the http components world but I need to use it for a >>> simple case I need to deal with. What I need to do is : >>> >>> >>> 1 - send a request using https to a remote server with a POST method >>> 2- pass parameters to this request (key/value pairs) >>> 3 - get a response back and read the response parameters >>> >>> I tried to read through the examples but I can't find an easy way to do >>> this, I feel a little bit lost in the API. Could anyone point me to the >>> right direction? >>> >>> Many thanks!! >>> >>> >>> Patrick >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: robert49@example.com >>> For additional commands, e-mail: robert49@example.com >>> >> >> -- >> [web] http://www.odi.ch/ >> [blog] http://www.odi.ch/weblog/ >> [pgp] key 0x81CF3416 >> finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: robert49@example.com >> For additional commands, e-mail: robert49@example.com >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: robert49@example.com > For additional commands, e-mail: robert49@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 21:00:24 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 59731 invoked from network); 2 Feb 2009 21:00:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 21:00:24 -0000 Received: (qmail 15030 invoked by uid 500); 2 Feb 2009 21:00:20 -0000 Delivered-To: robert49@example.com Received: (qmail 15000 invoked by uid 500); 2 Feb 2009 21:00:20 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 14989 invoked by uid 99); 2 Feb 2009 21:00:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 13:00:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 21:00:19 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id B3AFD234C4AA for <robert49@example.com>; Mon, 2 Feb 2009 12:59:59 -0800 (PST) Message-ID: <1815862237.1233608399734.JavaMail.jira@brutus> Date: Mon, 2 Feb 2009 12:59:59 -0800 (PST) From: "Sebb (JIRA)" <robert49@example.com> To: robert49@example.com Subject: [jira] Closed: (HTTPCORE-182) HttpConnection.shutdown() not always thread-safe In-Reply-To: <1191132536.1233530280984.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCORE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed HTTPCORE-182. ------------------------- OK, that should fix it. > HttpConnection.shutdown() not always thread-safe > ------------------------------------------------ > > Key: HTTPCORE-182 > URL: https://issues.apache.org/jira/browse/HTTPCORE-182 > Project: HttpComponents HttpCore > Issue Type: Bug > Reporter: Sebb > Fix For: 4.0-beta4 > > > The documentation says that the HttpConnection is generally not thread-safe, but that the shutdown() method is thread-safe. > However this is not the case at present for the methods: > org.apache.http.impl.SocketHttpClientConnection.shutdown() > org.apache.http.impl.SocketHttpServerConnection.shutdown() > It reads the socket from the instance variable "this.socket" which is not synchronised, final or volatile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: robert49@example.com For additional commands, e-mail: robert49@example.com From robert49@example.com Mon Feb 02 21:04:18 2009 Return-Path: <robert49@example.com> Delivered-To: robert49@example.com Received: (qmail 61420 invoked from network); 2 Feb 2009 21:04:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Feb 2009 21:04:18 -0000 Received: (qmail 19540 invoked by uid 500); 2 Feb 2009 21:04:18 -0000 Delivered-To: robert49@example.com Received: (qmail 19331 invoked by uid 500); 2 Feb 2009 21:04:17 -0000 Mailing-List: contact robert49@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:robert49@example.com> List-Unsubscribe: <mailto:robert49@example.com> List-Post: <mailto:robert49@example.com> List-Id: <dev.hc.apache.org> Reply-To: "HttpComponents Project" <robert49@example.com> Delivered-To: mailing list robert49@example.com Received: (qmail 19320 invoked by uid 99); 2 Feb 2009 21:04:17 -0000 Received: from
{'source': 'Apache Software Foundation Public Mail Archives'}