Hi Leander, For the moment according to the design of Synapse, it executes the fault sequence only for the errors that has been occurred within synapse environment but not for the transport level errors received from the client side. Instead this message should be injected into the out sequence of the proxy and if you have a send mediator there, you could be able to get the same response with the 304 or what ever the status code to the client side.
Do you think this has to invoke the fault sequence? In most of the cases what is required is to forward this response back to the client. Thanks, Ruwan On Wed, Jul 2, 2008 at 5:12 AM, <[EMAIL PROTECTED]> wrote: > For my next newb question: I have a proxy set up that looks like this: > > <sequence name="getURL" onError="myFault"> > <!-- big script that sets the message To: was here--> > <send> > <endpoint> > <default format="get" trace="enable"/> > </endpoint> > </send> > </sequence> > > <sequence name="myFault"> > <log level="full"/> > <send/> > </sequence> > > <proxy name="feed" transports="http"> > <target inSequence="inSeq" outSequence="setMessageType" > faultSequence="myFault"/> > </proxy> > > The proxy gets out to the message destination just fine and if the server > at the destination sends a 200 OK all is well. However, if the server comes > back with a 'non-ok' code like 304, it gets logged that an unexpected http > status was recieved, but the myFault sequence never runs (so far as I can > tell - nothing is logged, anyhow). Did I miss something here? > > Thanks again, > > -Leander > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
