« Return to Thread: http transport problem

Re: http transport problem

by Chathura Ekanayake :: Rate this Message:

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Andrew,

I am using Mule 1.4.1

Yes, the sequence is as you have mentioned, HEAD message before the GET.
But is there a way to avoid sending HEAD messages?

Thanks,
Chathura

On 6/15/07, Andrew Perepelytsya <aperepel@...> wrote:

What is the Mule version? In fact, the sequence should be the opposite, HEAD, then GET.

Andrew

On 6/14/07, Chathura Ekanayake <cce.axis@...> wrote:
Hi,

I am using a http endpoint in the outbount router of a mule component to send messages to a backend server. When this
endpoint is sending messages, the first message is sent as a http GET method and the response to that
is received. But the endpoint sends another message using http HEAD method without any content.
Is there a way to stop the mule endpoint from sending the HEAD message?

my configuration is as follows:

<model name="MyMuleModel">

        <mule-descriptor name="MyMule" implementation="org.mule.components.simple.BridgeComponent">

            <inbound-router>
                <endpoint address="http://localhost:8090/services" transformers="Xsltin" responseTransformers="Xsltout" synchronous="true"/>
            </inbound-router>

            <outbound-router>
                <router className="org.mule.routing.outbound.OutboundPassThroughRouter">
                    <endpoint address=" http://localhost:9000/soap/SimpleStockQuoteService" synchronous="true"/>
                </router>
            </outbound-router>

        </mule-descriptor>

    </model>

Regards,
Chathura C. Ekanayake

« Return to Thread: http transport problem