Hi there,
I have read (I think) all threads on HTTP file posts to the IS, but unfortunately no one speaks about getting the actual InputStream to create the mime object. I have found a thread about creating custom content handlers but the sample code given has quite a number of bugs in it, and in the end does not do the job
Problem is that after posting a form (multipart/form-data) to the IS, the only way I can get the InputStream from the pipeline is by using (IData)pi.getProtocolProperty(“contentStream”);… When checking the info in the stream (by converting to a byteArray), it looks as if I am missing some headers.
The string looks like this:
------------------------7d33b21b40244-- 4 Content-Disposition: form-data; name=“sourceID” 11 -----------------------------7d33b21b40244 Content-Disposition: form-data; name=“fileID” 22 -----------------------------7d33b21b40244 Content-Disposition: form-data; name=“file”; filename=“D:\sqlnet.log” Content-Type: application/octet-stream (snip)
I am not quite sure why the boundaries are still present, as I assumed they would be removed from the stream before being put into the pipeline. Do you have any additional info on this or am I just going down the wrong track in handling this problem?
PS. Currently using IS 6.0.1 SP1 on both Unix & Windows 2K
Many thanks, Chris
#webMethods#webmethods-Protocol-and-Transport#Integration-Server-and-ESB