Hi
Hi Sergey, Like I mentioned before, I control the client making the request and can set the content-type of the request to whatever I want. I started with it as application/octet-stream. Right now I just have an arbitrary value in there as a test, but I'm going to change it back, because I think application/octet-stream is correct. The extra bytes I'm seeing contain the other parts of the request, including the content disposition, the content-type, the name, and the filename.
Are these values contained in the actual payload or are they represented by HTTP headers ? If it's the latter then I'd surprised if they were passed to the byte[] array, if it's the former then I believe the only way to strip them off at the moment is to provide a custom MessageBodyReader for a byte[] type which would remove them from the input stream and then pass to the application. InputStream can be more efficient as an input parameter in this case as you might be able to filter out (in you custom MessageReader for InputStream) the extra data you don't need. Does it help ? Cheers, Sergey
The thing that makes this request is in Lua, a language I'm not yet proficient at, so pardon me if I bumble a little. I'm writing a plugin for Adobe Photoshop Lightroom that will submit photos to my application. -Chris
---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
