Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 64100 invoked from network); 17 Nov 2010 08:41:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Nov 2010 08:41:59 -0000 Received: (qmail 18588 invoked by uid 500); 17 Nov 2010 08:42:30 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 18283 invoked by uid 500); 17 Nov 2010 08:42:29 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 18268 invoked by uid 99); 17 Nov 2010 08:42:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Nov 2010 08:42:29 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of moleyharey@gmail.com designates 74.125.83.43 as permitted sender) Received: from [74.125.83.43] (HELO mail-gw0-f43.google.com) (74.125.83.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Nov 2010 08:42:21 +0000 Received: by gwb17 with SMTP id 17so988851gwb.30 for ; Wed, 17 Nov 2010 00:42:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=rJQ/itlbfifw16Gv7LM/IdkIZgHogUtjtNLM71ghHGk=; b=MFnjFBjJi4pRV4JQzwJAlJ8Jyje2WB9YNxuOAgalqw01DJxlntaEtRKIaU526+oI9m v3TqYH9LHhtI2awVxoYEDdu7Bm5KBSUXDtrmBCIhkncMEBw2xc/BSQlCgRMqXYXDB1XU HfGX5TFI9pj1tzGgV8AeA+76CBIHxJkXIxMqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=vLknfwZnaiipvBwB7N/JFDG93L/JHPVgqhULLrFWDXqeGbDHTQHNEVxovRlGkMAQDq bjiyCbAKi5tiCvPnEEUqTru9Nh9dsSCcDRuhIOqibxjbzMzkvWv1Y6cqWKGpvTTEmgSz +tKpyr7uLRB4QCWHGW1W2LVZjD8aTsKnFmY0I= MIME-Version: 1.0 Received: by 10.90.59.2 with SMTP id h2mr11130994aga.115.1289983320812; Wed, 17 Nov 2010 00:42:00 -0800 (PST) Received: by 10.91.186.10 with HTTP; Wed, 17 Nov 2010 00:42:00 -0800 (PST) Date: Wed, 17 Nov 2010 09:42:00 +0100 Message-ID: Subject: Can HTTP Commons API manage SSL certificates? From: Moley Harey To: user@commons.apache.org Content-Type: multipart/alternative; boundary=0016363106c99a6c9404953ba52d X-Virus-Checked: Checked by ClamAV on apache.org --0016363106c99a6c9404953ba52d Content-Type: text/plain; charset=ISO-8859-1 Hi folks, I have a some web services installed in Tomcat which must be accessed using HTTPS protocol and I was wondering if it is possible to use Apache Http Commons API for that, I have used this library for simple HTTP requests and works well. My main concern is regarding the SSL certificates, I have a self generated certificate using keystore tool and the client should automatically accept that certificate every time an HTTPS is done. Can I do that with Http Commons API? How can I do that? Thanks in advance, Mh --0016363106c99a6c9404953ba52d--