Thank you for replying.
To be more specific, it is only when I try SOAP with attachments that Axis2 fails to find the \r\n sequence. Normal RPC works nicely. However, I know for a fact that somebody left off a \r, but only when packaging the parts for SOAP with attachments.
It seems that the bad data is coming from MIME::Entity, which does not use the BOUNDARY_DELIMITER you mention, and has 29 \n characters. Perhaps all of these are illegal.
My client's expectation is to be able to "perl -MCPAN -e shell" and "install" . I'm new to perl and I would not trust myself to fix something like this (nor would you want me to :-)) , nor would my client expect to pay me to do this. I also am not aware of how ownership of modules works.
It would be nice to pass along the message.
It does not look like I'll be doing attachments.
In reply to Re^2: SOAP::Lite or MIME::Entity generate invalid HTTP line endings
by Tardigrade4
in thread SOAP::Lite or MIME::Entity generate invalid HTTP line endings
by Tardigrade4
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |