Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E50710211 for ; Tue, 25 Nov 2014 14:28:45 +0000 (UTC) Received: (qmail 93656 invoked by uid 500); 25 Nov 2014 14:28:45 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 93609 invoked by uid 500); 25 Nov 2014 14:28:45 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 93596 invoked by uid 99); 25 Nov 2014 14:28:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 14:28:44 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of avraham2@gmail.com designates 209.85.217.178 as permitted sender) Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com) (209.85.217.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 14:28:39 +0000 Received: by mail-lb0-f178.google.com with SMTP id f15so694982lbj.9 for ; Tue, 25 Nov 2014 06:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=J9bHgBNY84JwTcMo92nIQfnJ7TAhekmhiURCy/LwKac=; b=tYHIXJau7DWcAcS2UKexxLnHnJBVy2CY566fvp7uXBFtp4cvRr8nl5w/jA6EfoTkcT 460UxCYPyLABdK8BTiYdgBvEKZ1OlltBXpMBusJOI7oPzEbPuoomdLqjFMVpDF8ivGnE M1Q4EHtaF2Ko450PRXpFqpyg0oic08zArcAKezbN5Fk3q7FxUVdcXDyVK4sKT1F1aiZf l4tHVzukOl3UEThINkhZgcZbiwBkKLPgUiB9DiDJr9jMV8I0mne54Xnk2xs80vxNakuB qkbuD81Hnnc0pA5B0bhSHpvq3TdlWV5lSQ8jSk9JhbEpnIbh5lRL+a5gsHFVma1CQx3g 7Swg== X-Received: by 10.112.139.196 with SMTP id ra4mr26492135lbb.95.1416925663232; Tue, 25 Nov 2014 06:27:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.11.6 with HTTP; Tue, 25 Nov 2014 06:27:22 -0800 (PST) From: Avi Hayun Date: Tue, 25 Nov 2014 16:27:22 +0200 Message-ID: Subject: When should I use the ClientAuthentication ? To: HttpClient User Discussion Content-Type: multipart/alternative; boundary=001a11c33fccd487fe0508afb68a X-Virus-Checked: Checked by ClamAV on apache.org --001a11c33fccd487fe0508afb68a Content-Type: text/plain; charset=UTF-8 I am maintaining a Web Crawler. I want to integrate crawling of sites which have username/password zones. I successfully integrated FORM based authentication. I want to integrate also the ClientAuthentication I can see here: https://hc.apache.org/httpcomponents-client-ga/httpclient/examples/org/apache/http/examples/client/ClientAuthentication.java But, in order to check it out I need a scenario - a site with a zone protected by this type of authentication. Can anybody supply me with an example where I can use this ClientAuthentication in order to crawl ? --001a11c33fccd487fe0508afb68a--