Disclaimer: same issue has been treated without solution in node_id 806606. I'm trying to integrate a client webservice, that allows ticket opening requests via SOAP. Everything works great, except when I try to attach file in the SOAP::Lite message, using SOAP::Packager and MIME::Entity. I deepened the issue, and I confirm that the problem is caused by the remote server expecting sequences of CRLF and not '\n' for line ending. Here is a snippet of the code I'm using:
.. my $ent = build MIME::Entity Type => "application/octet-stream", Encoding => "binary", Path => "/usr/share/httpd/icons/small/uu.gif", Filename => "uu.gif", Disposition => "attachment", my $method = SOAP::Data->name('OpCreate') ->attr({'Request_Urgency' => $options{'urgency' +}}); my $header = SOAP::Header ->name('AuthenticationInfo' => \SOAP::Header->value(@logininfo) ); print Dumper \$ent; #exit; my $result = SOAP::Lite ->packager(SOAP::Packager::MIME->new) ->parts([$ent]) ->proxy($create_proxy, ssl_opts => [ SSL_verify_mode => 1, S +SL_ca_file => '/root/Firefox_CERT/CUSTOMERROOTCA2'] ) ->call($header, $method => @data) ; ..
I'm looking forward to change things in my code, to generate/change on the fly needed ending characters. I manually test things with curl using raw data coming from SOAP::Lite trace output as raw file input and I confirm that is sufficient to use "unix2dos" on the ASCII part of the resulting file to see things working as expected. Hacky solutions are welcome, Thanks for any hints
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |