This time I'm not using SOAP::Lite because of it's lack for multipart MIME messages/Attachments. What that has done, is helped me learn a lot more about this stuff. ;)my $soap_request = <<END; POST /insuranceClaims HTTP/1.1 Host: 10.7.2.33 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml +; start="<cid:foo4\@bar.net>" Content-Length: 1024 SOAPAction: http://10.7.2.33:2738/Hello Content-Description: This is the optional message description. --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <cid:foo4\@bar.net> Content-Location: http://10.7.2.33:2738/Hello <?xml version='1.0' ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/env +elope/"> <SOAP-ENV:Body> <ns1:hi> <upload_file href="http://10.7.2.33:2738/upload_file.txt"/> <name>Thomas</name> </ns1:hi> </SOAP-ENV:Body> </SOAP-ENV:Envelope> --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <http://10.7.2.33:2738/upload_file.txt> Content-Location :http://10.7.2.33:2738/upload_file.txt ...binary TIFF image... --MIME_boundary-- END
In reply to Re: Re: SOAP and multiple client platforms
by one4k4
in thread SOAP and multiple client platforms
by one4k4
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |