Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27694404.post@talk.nabble.com>
Date: Mon, 22 Feb 2010 13:05:19 -0800 (PST)
From: Christian Mueller <christian.mueller@gmail.com>
To: users@camel.apache.org
Subject: Re: Using HTTPS in camel-http when remote side has self-signed cert
In-Reply-To: <27689918.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <2aeb7abd0910151512x22693ceex72ff15bcc3b3d08d@mail.gmail.com>
 <4AD93D8D.5000107@gmail.com> <27639063.post@talk.nabble.com>
 <27689918.post@talk.nabble.com>


Yogesh,
if you have a look on org.apache.commons.httpclient.protocol.Protocol, you
will see, that registerProtocol stores the protocol in a HashMap. Using the
same key "https" overrides the first registered protocol:

public class Protocol {
    private static final Map PROTOCOLS = Collections.synchronizedMap(new
HashMap());

    public static void registerProtocol(String id, Protocol protocol) {
        if (id == null) {
            throw new IllegalArgumentException("id is null");
        }
        if (protocol == null) {
            throw new IllegalArgumentException("protocol is null");
        }

        PROTOCOLS.put(id, protocol);
    }
}

Regards,
Christian
-- 
View this message in context: http://old.nabble.com/Using-HTTPS-in-camel-http-when-remote-side-has-self-signed-cert-tp25916878p27694404.html
Sent from the Camel - Users mailing list archive at Nabble.com.