Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 89776 invoked from network); 4 Feb 2008 06:17:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2008 06:17:03 -0000 Received: (qmail 91049 invoked by uid 500); 4 Feb 2008 06:16:52 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 90967 invoked by uid 500); 4 Feb 2008 06:16:51 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 90931 invoked by uid 99); 4 Feb 2008 06:16:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Feb 2008 22:16:51 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of samindaa@gmail.com designates 209.85.198.189 as permitted sender) Received: from [209.85.198.189] (HELO rv-out-0910.google.com) (209.85.198.189) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 06:16:21 +0000 Received: by rv-out-0910.google.com with SMTP id c24so1277237rvf.28 for ; Sun, 03 Feb 2008 22:16:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=mmE1PnPDfkbuxDOFFgNyG8Ib7B7qhc77ePRd0vQzxXk=; b=rSbxRvW85czCaexFztcBWgM1cUlj5xBLriq6nlAzTY4iJn2rgg+81HVR055u+1cka0c5WG8kLKwOxwSod9gxanYDqsgXbB9IBDtV0GKvQIFkF/XWxM+xC6WyNGKWowfhvISzzr2LVEqMgCS2o1aGStaRlBDUEGKXHS+BaMlLCgs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=TOEK2JcJqdngDH2YvQnmQgfo+/Dbtv3guivBTd1qTp9YJoWhlmYNt/Y5pooDgzsLMAhnFyT7MnMWFNtmSRIDfVn4l6wVRotd0XnrxUiK2N9/AUVqs6ZQgpJw+hsWV1JSu4VEfEBnZys6/vJFBBI91TLwzJ4sj/gWuA68701nDn0= Received: by 10.141.141.3 with SMTP id t3mr4445983rvn.226.1202105787480; Sun, 03 Feb 2008 22:16:27 -0800 (PST) Received: by 10.141.13.18 with HTTP; Sun, 3 Feb 2008 22:16:27 -0800 (PST) Message-ID: Date: Mon, 4 Feb 2008 11:46:27 +0530 From: "Saminda Abeyruwan" To: axis-dev@ws.apache.org Subject: Re: AxisFault: Transport error: 403 Error: Forbidden In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3566_23843081.1202105787477" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_3566_23843081.1202105787477 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, When you invoke the ws using https, your client side axsi2.xml needs to provide following, HTTP/1.1 chunked true for synchronous invocations. Thank you Saminda On Jan 29, 2008 9:36 AM, dd du wrote: > Hi, all, > > I have developed and deployed axis2-based webservice into my webserver > (Netscape Enterprise Server), my web service client can access and call it's > service over HTTP connection, now we need to use HTTPS (SSL) connection, > after I setup my certificate with both my web server and my browser, I can > use https connection to access the axis2 happyaxis.jsp and my webservice > wsdl file, and my other web applications, I did not change anything to the > axis2 configuration including axis2.xml, but when my web service client > called my web service, it threw org.apache.axis2.AxisFault: Transport > error: 403 Error: Forbidden. > > Questions: > 1. do I need to change the axis2.xml file to configure the transportsender > and transportreceiver, or anything else? > 2. After I debug into the code, it called open source HttpClient, and > HttpMethodDirector which has a method: private void authenticateHost(final > HttpMethod method), inside this call, there is a code block: > AuthScheme authscheme = authstate.getAuthScheme(); > LOG.debug("authenticateHost authscheme==["+authscheme+"]"); > if (authscheme == null) { > return; > } > > Now I can see when this code block is called, the authscheme is null, so > it will never do authentication to the host, so how can I setup axis2 to > have the scheme? > > Thanks in advance. > Dave > > -- Saminda Abeyruwan Senior Software Engineer WSO2 Inc. - www.wso2.org ------=_Part_3566_23843081.1202105787477 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,

When you invoke the ws using https, your client side axsi2.xml needs to provide following,

<transportSender name="https"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>
        <!-- This parameter has been added to overcome problems encounted in SOAP action parameter -->
        <parameter name="OmitSOAP12Action">true</parameter>
    </transportSender>

for synchronous invocations.

Thank you

Saminda



On Jan 29, 2008 9:36 AM, dd du <davidkdu@gmail.com> wrote:
Hi, all,
 
I have developed and deployed axis2-based webservice into my webserver (Netscape Enterprise Server), my web service client can access and call it's service over HTTP connection, now we need to use HTTPS (SSL) connection, after I setup my certificate with both my web server and my browser, I can use https connection to access the axis2 happyaxis.jsp and my webservice wsdl file, and my other web applications, I did not change anything to the axis2 configuration including axis2.xml, but when my web service client called my web service, it threw org.apache.axis2.AxisFault: Transport error: 403 Error: Forbidden.
 
Questions:
1. do I need to change the axis2.xml file to configure the transportsender and transportreceiver, or anything else?
2. After I debug into the code, it called open source HttpClient, and HttpMethodDirector which has a method: private void authenticateHost(final HttpMethod method), inside this call, there is a code block:
AuthScheme authscheme = authstate.getAuthScheme();
  LOG.debug("authenticateHost authscheme==["+authscheme+"]");
        if (authscheme == null) {
            return;
        }
      
Now I can see when this code block is called, the authscheme is null, so it will never do authentication to the host, so how can I setup axis2 to have the scheme?
 
Thanks in advance.
Dave
 



--
Saminda Abeyruwan

Senior Software Engineer
WSO2 Inc. - www.wso2.org ------=_Part_3566_23843081.1202105787477--