Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 741A8D42A for ; Tue, 28 May 2013 13:45:43 +0000 (UTC) Received: (qmail 80985 invoked by uid 500); 28 May 2013 13:45:43 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 80814 invoked by uid 500); 28 May 2013 13:45:42 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 80681 invoked by uid 99); 28 May 2013 13:45:41 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 13:45:41 +0000 Date: Tue, 28 May 2013 13:45:41 +0000 (UTC) From: "raise (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HTTPCLIENT-1357) Problem using HTTPS when using proxy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HTTPCLIENT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668303#comment-13668303 ] raise commented on HTTPCLIENT-1357: ----------------------------------- Thanks, Oleg > Problem using HTTPS when using proxy > ------------------------------------ > > Key: HTTPCLIENT-1357 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1357 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: HttpClient > Affects Versions: 4.2.5 > Environment: Use a repacked httpclient (repacked by jarjar) version 4.2.5 on android 2.2.2 > Reporter: raise > Fix For: 4.2.6, 4.3 Beta2 > > > Problem described at: http://code.google.com/p/android/issues/detail?id=2690. The fix is to set default port for scheme to avoid passing -1 as port, which would cause an IllegalArgumentException. > In method updateSecureConnection, located at file org.apache.http.impl.conn.DefaultClientConnectionOperator.java, line 233, should use schm.resolvePort(target.getPort()) instead of target.getPort() to avoid passing -1 as port. In android, ther is an patch review at https://android-review.googlesource.com/#/c/15755/1/src/org/apache/http/impl/conn/DefaultClientConnectionOperator.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org