HTTP chunking

View: New views

4 Messages — Rating Filter: Alert me

HTTP chunking

by Gerhard Maree :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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

I am responding to SOAP message using cxf.

Is it possible to turn HTTP chunking of for the server reponse?

Thanks

Gerhard

Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093?
If you don't have web access, the disclaimer can be mailed to you on request.
Disclaimer requests to be sent to it-security@...

Re: HTTP chunking

by rotten :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On a related note, I've noticed that whenever I hit an inbound HTTP endpoint with HTTP 1.0, it blows up with chunking errors. I've been able to get the users of our ESB to switch to HTTP 1.1 so far. However, in the near future I'm going to have to be able to accept HTTP 1.0 because not all of my users can send HTTP 1.1.

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).

Gerhard Maree wrote:

I am responding to SOAP message using cxf.

Is it possible to turn HTTP chunking of for the server reponse?

Re: HTTP chunking

by Andrew Perepelytsya :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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:

Try to do it yourself, and we'd be happy to provide technical assistance through lists.
Contact MuleSource support to have it fixed/enhanced for you, thus allocating a portion of available resources to your needs.

HTH,
Andrew

Re: HTTP chunking

by Benj :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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