On Mon, Jan 07, 2002 at 11:11:06PM +0100, Christian Gross wrote: > I have been building a SOAP Wrapper module for Apache 2.0. When an error > occurs within the SOAP call a SOAP specific error message is generated. > > In the 1.2 SOAP spec there is a default HTTP binding implementation. This > means when you generate a SOAP fault most likely you will generate an HTTP > 500 error. The problem is as follows. If you generate an error 500 from a > module Apache goes into a ap_die sequence, which causes an internal > redirect. This means all of the SOAP error content that I have generated > is thrown out. And instead a default error mechanism is used. The problem > with this is that I would need to store the SOAP errors on a temporary > stack for further reference in the internal redirection.
500 is not a reasonable error to return. You can define a custom response code or have the handler bypass HTTP by sending the raw response and returning DONE. > How is it possible to not make Apache go into the default error handling > mechanism? Or am I missing something really obvious? SOAP 1.2 is not HTTP compliant. Not really helpful, but now you know why it is a bad idea. ....Roy
