Adam Retter <[email protected]> writes: > Hi Norm, Hi Adam. Thanks for the example; you’ve threaded the needle better than I did. Maybe it’s good enough, but it’s still not exactly what I was hoping for.
> final FormBodyPart part1 = FormBodyPartBuilder.create()
> .setName("part1")
The requirement that parts have a name is a form requirement, not a
multipart requirement.
> On my system that produces a HTTP Request like:
>
> POST / HTTP/1.1
> Content-Length: 456
> Content-Type: multipart/form-data; boundary=ZQwFLuoO6V1SFdqg2lI6DaVwlvKIZjj2Pb
I can change this content-type by calling .setContentType() on the entity
builder,
however:
> Content-Disposition: form-data; name="part1"
Every part gets this content-disposition which is clearly bogus for
non-form multipart messages.
Bogus but perhaps harmless. I’m going to run with it and see what
happens. I’ll fail all of the XProc multipart tests of course, but…
Be seeing you,
norm
--
Norman Walsh <[email protected]> | So, are you working on finding that bug
http://nwalsh.com/ | now, or are you leaving it until later?
| Yes.
signature.asc
Description: PGP signature
