about.
John Bedell
From: Jain, Prateek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 12:46 PM
To: axis-user@ws.apache.org
Subject: RE: HTTP/1.1 400 No client certificate chain in this request
Ouch! I mean ho
Ouch! I mean how r u accessing that WS?
Prateek
From: John Bedell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 12:39 PM
To: axis-user@ws.apache.org
Subject: RE: HTTP/1.1 400 No client certificate chain in this request
I would
@ws.apache.org
Subject: RE: HTTP/1.1 400 No client certificate chain in this request
Try removing default jboss WS implementation and integrating/using AXIS2
engine. Hope, it works for u guys.
Regards,
Prateek
From: John Bedell [mailto:[EMAIL PROTECTED
Subject: RE: HTTP/1.1 400 No client certificate chain in this request
I'm not entirely sure. But I don't see any Axiss JARs included in the
package they sent for running the JBoss server, so I doubt they are
using it.
John
From: Jain, Prateek [mai
M
To: axis-user@ws.apache.org
Subject: RE: HTTP/1.1 400 No client certificate chain in this request
Just a weird question:
Are u suing default jboss web service engine or have integrated axis2
engine with its servlet container?
Regards,
Prateek
-user@ws.apache.org
Subject: HTTP/1.1 400 No client certificate chain in this request
Our setup:
We have an Axis2 1.3 web service client hitting a 3rd party web service
running on a JBoss server w/ Apache Coyote. We do not know what
package(s) were used to developer the server-side.
We need to
greatly appreciated.
Results with 4-5 updates
The header:
2008/11/18 16:33:58:081 EST [DEBUG] header - << "HTTP/1.1 500 Internal
Server Error[\r][\n]"
2008/11/18 16:33:58:081 EST [DEBUG] header - << "Server:
Apache-Coyote/1.1[\r][\n]"
2008/11/18 16:33:58:081 EST [
Hi Paul,
Thanks for your quick reply.
So it could be, that our proxy server does not support HTTP/1.1 - or to be
specific "Chunking" and returns this error message back to the caller - me.
That is indeed a great tip. I will check with our network guys on Monday!
Thanks again!
Stefan
Its not the Axis2 client reporting Not Implemented. Its either the
proxy or the server (Hard to tell which without seeing a wire trace or
the logs from those systems). I'm guessing its the proxy. Axis2 is
sending the message successfully and its the other system that can't
handl
-Not Implemented Exception. Strange, isn't it?
So I started to google and I got the advice to use HTTP/1.0 instead of
HTTP/1.1 and set the transfer-encoding from chunked to false. (See here for
details:
http://archives.devshed.com/forums/apache-92/axis2-http-proxy-setting-1846399.html
@ws.apache.org
Onderwerp: Re: http 1.1 chunking and large messages using axis2 1.3
On Dec 20, 2007 2:44 PM, Erwin Reinhoud <[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
> I am wondering how large message (lets say >0,5GB) are handled when it is
> sent chunked over HTTP 1.
On Dec 20, 2007 2:44 PM, Erwin Reinhoud <[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
> I am wondering how large message (lets say >0,5GB) are handled when it is
> sent chunked over HTTP 1.1 and there is a network interruption.
>
> Does it support some kind of rest
Hello All,
I am wondering how large message (lets say >0,5GB) are handled when it is sent
chunked over HTTP 1.1 and there is a network interruption.
Does it support some kind of restarts, allowing the transfer to continue where
it left off if it is interrupted, rather than starting over f
-
- Original Message
From: "Walker, Jeff" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, October 8, 2007 11:27:23 AM
Subject: RE: Axis 1.4 configuration to use HTTP/1.1
DIV {
MARGIN:0px;}
Hi Mario,
Shadab got his problem solved. (He
wanted to use HTTP 1.1 in
27;ll make this change first and go from
there.
Thanks again for the help!
Mario-
- Original Message
From: "Walker, Jeff" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, October 8, 2007 11:27:23 AM
Subject: RE: Axis 1.4 configuration to use HTTP/1.1
Hi Mario,
Shadab got his problem solved. (He wanted to use HTTP 1.1 in Axis 1.4
and do it programmmatically on the clientside). the solution he emailed
to me is:
Hi Jeff,
Thank you so much for all the info..
I have succesfully implemented the second alternative of using -
CommonsHTTPSender
direction?
Thanks!
Mario-
- Original Message
From: Shadab <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Wednesday, October 3, 2007 2:36:50 AM
Subject: Axis 1.4 configuration to use HTTP/1.1
Hi All,
Please let me know if there is any way to configure Axis1.4 such that it
use
essage-
From: Walker, Jeff [mailto:[EMAIL PROTECTED]
Sent: Thursday, 4 October 2007 2:35 AM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.4 configuration to use HTTP/1.1
Hi,
So, I tried playing around with the http version. Theoretically, you
should be able to set a property on the binding (o
Hi,
So, I tried playing around with the http version. Theoretically, you
should be able to set a property on the binding (or at least, the Call
object) to switch between http 1.0 and http 1.1 This did not work.
I could only manage to change to http 1.1 by editing the method
writeToSocket() in
Hi All,
Please let me know if there is any way to configure Axis1.4 such that it
uses HTTP/1.1 instead of HTTP/1.0
The request from the soapclient (implemented using service stub) lands with
Axis/1.4 which in turn by default presumably uses HTTP/1.0.
Can't this be changed somehow
ht need to disable chunked transfer encoding
=
-Original Message-
*From:* Joan Barrull [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, 12 July 2007 1:29 AM
*To:* axis-user@ws.apache.org
*Subject:* How to set HTTP/1.1 with Axis1.4
Hi guys,
I am using Axis 1.4. My client, generated through wsdl
transfer encoding.
So you might need to disable chunked transfer encoding
=
-Original Message-
From: Joan Barrull [mailto:[EMAIL PROTECTED]
Sent: Thursday, 12 July 2007 1:29 AM
To: axis-user@ws.apache.org
Subject: How to set HTTP/1.1 with Axis1.4
Hi guys,
I am using Axis 1.4. My cl
through the tcpmonitor, I get the
following header:
POST /isadpt_grupo1 HTTP/1.0
How can I modify my code in order to send through HTTP/1.1 instead of
HTTP/1.0?
Thanks in advance,
joan
sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Jorge Fernandez
To: axis-user@ws.apache.org ; Martin Gainty
Sent: Thursday, June 21, 2007 4:41 PM
Subject: Re: HTTP/1.1 400 Bad Request
Hola
es:
The correct one with standalone axis:
HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml;
action="http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault";
Server: Simple-Server/1.1
Transfe
r the description element namespace and that
the final character after envelope in one case appears in the following line.
This are the messages:
The correct one with standalone axis:
HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-Type: applicatio
order of HTTP header, the prefix for the description element namespace and that
the final character after envelope in one case appears in the following line.
This are the messages:
The correct one with standalone axis:
HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-
me minimal changes in the
order of HTTP header, the prefix for the description element namespace and that
the final character after envelope in one case appears in the following line.
This are the messages:
The correct one with standalone axis:
HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun
]
Gesendet: Montag, 11. Juni 2007 17:42
An: axis-user@ws.apache.org
Betreff: Re: HTTP/1.1 400 Bad Request
I would verify your
AxisService is operational (go to Axis Admin and verify the service is
displayed)
verify the operation name
HTTP/1.1 400 Bad RequestI would verify your
AxisService is operational (go to Axis Admin and verify the service is
displayed)
verify the operation name is correct
verify the parameters for the Service are correct
But this specific error has is a genuine IBM bug ..It looks as if you will need
Hi,
when an exception occurs on server side I receive the Fault-Response with HTTP
Code 400 instead of 500.
Axis 2 then simply returns Bad Request but not the original server exception.
Any ideas why I get the 400?
Here is the response message:
HEADER:
--
HTTP/1.1
on web site. Interestingly, I can sucessfully invoke
most of them but for some of them I get this error:
INFO: Discarding unexpected response: HTTP/1.1 100 Continue
org.apache.axis2.AxisFault: HTTP Transport error : '404' - 'File not
found'; nested exception is:
org.ap
Hi,
With my generic Axis client code, I am trying to invoke some services
available on strikeIron web site. Interestingly, I can sucessfully invoke
most of them but for some of them I get this error:
INFO: Discarding unexpected response: HTTP/1.1 100 Continue
org.apache.axis2.AxisFault: HTTP
ll to log
into the service, which returns success (logged in), and I get an error message
from axis:
"Discarding unexpected
response: HTTP/1.1 100 Continue"
Then I make my second call
(the action call) and I receive a "not logged in" error from the
service follow by
gt; Von: Eran Chinthaka <[EMAIL PROTECTED]>
> An: axis-user@ws.apache.org
> Betreff: Re: Frustrating experience with Axis2 due to HTTP 1.1 and Chunked
> Transfer-Encoding
>
>> Dapeng Wang wrote:
>>> Hi, Eran,
>>>
>>> thank you for your hint. Bu
he.org
Betreff: Re: Frustrating experience with Axis2 due to HTTP 1.1 and Chunked
Transfer-Encoding
> Dapeng Wang wrote:
> > Hi, Eran,
> >
> > thank you for your hint. But there seems to be no constant called
> CHUNKED anymore in the class. Neither is there any constant c
Dapeng Wang wrote:
> Hi, Eran,
>
> thank you for your hint. But there seems to be no constant called CHUNKED
> anymore in the class. Neither is there any constant called
> NTLM_AUTHENTICATION as documented on the wso2 website.
> HTTPConstants.HEADER_TRANSFER_ENCODING_CHUNKED is also not the rig
rating experience with Axis2 due to HTTP 1.1 and Chunked
Transfer-Encoding
> Hi Dapeng,
>
> Can u try disabling chunking?
> (http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters#CHUNKED)C
>
> - EC
>
> Dapeng Wang wrote:
> > Hi,
> >
> > I
he failure at first sight.
>
> TCPMON captures following request and response:
> Request:
> POST /axis2/services/version HTTP/1.1
> User-Agent: Axis/2.0
> SOAPAction: ""
> Host: localhost:8081
> Transfer-Encoding: chunked
> Content-Type: text/xml; charset=U
by an OMException, so that you can't see the real reason of
the failure at first sight.
TCPMON captures following request and response:
Request:
POST /axis2/services/version HTTP/1.1
User-Agent: Axis/2.0
SOAPAction: ""
Host: localhost:8081
Transfer-Encoding: chunked
Content-Type: tex
I am using Axis 1.2.1 for my Web Service client. I
am issuing HTTP 1.0 requests and the server is sending me HTTP 1.1 responses.
Can I configure my client to use HTTP 1.1 instead of 1.0?
Thank you
Fady
Hi all, i have interoparablity problems with one webservice client that
need content-length on web services responses.
As i read on RFCs, axis source code, and google searches, servlets
container as tomcat use transfer-encoding "chunked" if axis don't call
setContentLength on AxisServlet Response.
(MessageContext.HTTP_TRANSPORT_VERSION,HTTPConstants.HEADER_
PROTOCOL_V11);
/Best regards
Rickard S
Hi
I'am relatively new to Axis.
I need to configure my axis Client to use HTTP/1.1 instead of HTTP/1.0.
I've searched this List and the Web but cannot find any description on
how to do this.
Can an
Hi
I'am relatively new to Axis.
I need to configure my axis Client to use HTTP/1.1 instead of HTTP/1.0.
I've searched this List and the Web but cannot find any description on
how to do this.
Can anyone point me in the correct direction here ?
Thanks
Clement
Hi,
I heard that it
requires some extra work to make Axis client work with HTTP/1.1. Let's assume it
works with HTTP/1.1, how does it take advantage of HTTP/1.1 's pipelinig feature
? Given the fact that each client call is a synchronized call. My
understanding is that even
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane)
Sent: Friday, April 08, 2005 1:39 PM
To: axis-user@ws.apache.org
Subject: Re: POST HTTP/1.1
Simon,
How do you reconfigure it to use CommonsHTTPSender? Do you
have an example please?
Also, would it be
t; Simon Fell wrote:
> > Change your sender config to use commonsHTTPSender instead of the
> > default HTTPSender class.
> >
> > Cheers
> > Simon
> >
> >
> >>-Original Message-
> >>From: Ada Lam [mailto:[EMAIL PROTECTED]
> >>
HTTPSender class.
Cheers
Simon
-Original Message-
From: Ada Lam [mailto:[EMAIL PROTECTED]
Sent: Friday, April 08, 2005 1:10 PM
To: axis-user@ws.apache.org
Subject: POST HTTP/1.1
Hi all,
I am currently using axis 1.2 RC3. I want to send SOAP message to
server via POST HTTP/1.1. However
Change your sender config to use commonsHTTPSender instead of the
default HTTPSender class.
Cheers
Simon
> -Original Message-
> From: Ada Lam [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 08, 2005 1:10 PM
> To: axis-user@ws.apache.org
> Subject: POST HTTP/1.1
>
&
Hi all,
I am currently using axis 1.2 RC3. I want to send SOAP message to
server via POST HTTP/1.1. However, axis is using POST HTTP/1.0.
I've tried to change it by doing:
call.getMessageContext().setProperty(org.apache.axis.MessageContext.HTTP_TRANSPORT_VE
50 matches
Mail list logo
