in reply to Re^3: Soap::Lite - returning lots of info
in thread Soap::Lite - returning lots of info

The worm has turned..

In order to make a 'clean' repro case I started pruning the code down to its most essential form. One thing I took out was the https: wrapper that I was using (HTTP::Daemon::SSL). The truncation issue has gone away!

Im looking at the return value(s) from my test package before it hits the 'send_response' and its intact.

Now Im digging into the docs for the SSL wrapper.

Further: it appears to be solely contingent on the SSL portion. If I wrap my SOAP package in HTTP::Daemon it works fine. Adding the ::SSL causes the fault.

Now I need to see if this is 'by design'.

EDIT: at this point Im guessing that because my client is sending the 'HTTP1.1' header the return value is getting sliced up. From the docs for HTTP::Daemon
If the client is HTTP/1.1 aware then we will use chunked transfer encoding for the response.
  • Comment on Re^4: Soap::Lite - returning lots of info

Replies are listed 'Best First'.
Re^5: Soap::Lite - returning lots of info
by ethrbunny (Monk) on Oct 25, 2007 at 12:52 UTC
    Addendum: I was able to see my return values being chopped into 0x3FFF pieces prior to being returned. Unf I was unable (given my time constraints) to figure out how to trap this situation on the client so that I could recombine the resultant parts prior to marshaling them back into my hash.

    Im guessing that the 'chunked transfer' is what's happening as I do see the 'HTTP1.1' header being sent.

    At this point its easier for me to restructure my server code to send smaller increments of data than to disassemble SOAP::Lite to get what I need from it. Its not the ideal solution but it will have to suffice for now.
[reply]

In Section Seekers of Perl Wisdom