File Upload to Java JSP page fails with "Malformed line after disposition: …"

[sparklemotion]

File Upload to Java JSP page fails with "Malformed line after disposition: …"

[subtleGradient]

removing this line http://github.com/tenderlove/mechanize/blob/0ddf33bf3903905461b727bba4f1f0db416e4041/lib/mechanize/form.rb#L356 solves the issue for me

[kaiiserni]

WOW, that helped me as well! Thanks subtleGradient!
I had this problem while talking to a .net server.
Can this be removed in the main library as well?

thanks!

[subtleGradient]

upvote this issue then?

[kaiiserni]

sure ;-)

[flavorjones]

Hi. I've read through the RFCs related to MIME headers, and I can't find anything that specifies that Content-type must appear after Content-disposition. Do you have a reference document that will help me understand what the underlying issue is?

If you could submit a test case for this, so that I could reproduce your issue, I might be able to decide whether this is truly a Mechanize issue.

[subtleGradient]

It's not a Mechanize issue, it's an issue in whatever Java code that is, but to work around them it'd be nice to change Mechanize since that's the only possible way to make it work with that server.

See the source code http://www-inf.int-evry.fr/~meunier/ProjetsIG3/TtImagesRep/node78.html

[kaiiserni]

It's indeed not an issue with Mechanize.
I have this problem only when talking to .net servers.
It would be a nice to have if we were able to switch the binary mode line on or off.

thanks for the followup!

[drbrain]

The Content-Transfer-Encoding may not be omitted at this time per RFC 2045 section 6.2 paragraph 6:

The proper Content-Transfer-Encoding label must always be used.

Choosing 7bit or 8bit would require inspecting the file contents to be sure it met the criteria of RFC 2045 section 2.

The content-transfer-encoding could be omitted if file contents were inspected to ensure the data was 7bit per RFC 2388.