[
https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509464
]
Jorge Fernández commented on AXIS2-2845:
----------------------------------------
That is half of the problem. I think that when the client reads the http
header, doesn't care about the SOAP message. I'm using SOAP 1.2.
But the other half is: why when Axis2 is used as standalone server, it sets the
HTTP header to 500 instead of 400 when throwing the same exception?
That was the reason that made me think that it wasn't a client's problem but
server's, and also the reason ot the title.
> Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
> ------------------------------------------------------------------------------
>
> Key: AXIS2-2845
> URL: https://issues.apache.org/jira/browse/AXIS2-2845
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2
> Reporter: Jorge Fernández
> Assignee: Glen Daniels
> Fix For: 1.3
>
> Attachments: exception.txt
>
>
> When I integrate Axis2 with Tomcat and I try to throw any exception, the
> response message is added a HTTP header meaning Bad Request and the exception
> in the SOAP message is OK but when my client sees the HTTP header doesn' t go
> on parsing the SOAP message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
