Hi,
I've the same problem with a php client which is in http 1.0.
There's no workaround to force HTTP 1.0 through Mule ? I'm using Mule 1.4.4.
I've tried to make a simple transformer which change the event context with http version at 1.0 but that no effect on outgoing requests which are still marked as HTTP 1.1.
My php client call a remote soap webservice proxied by a customized version of WSProxy component.
Regards,
Andrew Perepelytsya wrote:
Gerhard,
>
> If forcing chunking off fixes it, this would be a great feature.
>
> Otherwise, we are going to be stuck with Mule 1.4.x for the forseeable
> future (until the HTTP transport is fixed to support HTTP 1.0).
>
>
There are only 2 ways to fix this, as physically we can't accommodate every
request:
1. Try to do it yourself, and we'd be happy to provide technical
assistance through lists.
2. Contact MuleSource support to have it fixed/enhanced for you, thus
allocating a portion of available resources to your needs.
HTH,
Andrew
