[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-user
Subject:    RE: How to make Soap server send back response with Http status code = 400, bad request
From:       feng xie <xiefeng914 () yahoo ! com>
Date:       2005-09-29 19:07:23
Message-ID: 20050929190724.59221.qmail () web52215 ! mail ! yahoo ! com
[Download RAW message or body]

Simon:

Thanks for your reply. 

Does that mean 500 status code SHOULD also be used for
the case where Client is wrong to send a bad request.
In that case, it isn't really a "internal server error
".

Feng 

--- Simon Fell <sfell@salesforce.com> wrote:

> The use of a 500 status code to return a SOAP Fault
> is required by the
> SOAP 1.1 specification.
> 
> Cheers
> Simon 
> 
> -----Original Message-----
> From: feng xie [mailto:xiefeng914@yahoo.com] 
> Sent: Thursday, September 29, 2005 11:35 AM
> To: axis-user@ws.apache.org
> Subject: How to make Soap server send back response
> with Http status
> code = 400, bad request
> 
> A few days ago, I sent out an email asking for the
> possible http status
> code used by Axis server when sending back Soap
> response. I got back
> answers with a list of http status code:
> 
> 200 OK
> 202 Accepted
> 307 Temporary Redirect
> 400 Bad Request
> 405 Method Not Allowed
> 415 Unsupported Media Type
> 500 Internal Server Error
> 
> For my case, whenever my server side code raises a
> user defined
> expection which extends org.apache.axis.AxisFault,
> even for a client
> side error (such as bad request with wrong
> parameter), the Axis server
> sends back Soap fault with http status code of 500.
> Seems to me, status
> code of 500 ( internal server error ) doesn't fit
> very well some cases
> where the client sends wrong requests.
> 
> So, my new question is: how to let the Axis server
> send back Soap
> fault/response with Http status code of 4XX ( for
> instances, 400 for Bad
> Request).  The WS-I
> Basic Profile V1.0 says " R1126   An INSTANCE MUST
> use
> a "500 Internal Server Error" HTTP status code if
> the response message
> is a SOAP Fault.".
> 
> Should the server side code throw
> java.rmi.RemoteException for the case of Bad Request
> ?
> 
> Thanks in advance,
> Feng
> 
> 
> 
> 	
> 		
>
______________________________________________________
> Yahoo! for Good
> Donate to the Hurricane Katrina relief effort. 
> http://store.yahoo.com/redcross-donate3/ 
> 
> 
> 
> 



		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
[prev in list] [next in list] [prev in thread] [next in thread]