[HTTPCLIENT-1372] Content-Disposition header in form data does not adhere to RFC6266

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.5
• Fix Version/s: 4.3 Final
• Component/s: HttpClient (classic)
• Assignee: Karl Wright
• Reporter: Karl Wright
• Created: 14/Jun/13 09:15
• Updated: 20/Sep/16 19:32
• Resolved: 20/Jun/13 21:09

Description

The Content-disposition header, as it appears for an item of form data, does not allow for UTF-8 encoding as specified in RFC6266, as described here:

http://tools.ietf.org/html/rfc6266

This is causing ManifoldCF severe problems working in Japan with Solr, since Solr content extraction relies on accurate filenames in order to determine the likely document encoding.

A fix for the 4.2.x branch will be needed, I am afraid.

Issue Links

• is depended upon by: CONNECTORS-623 stream_size and stream_name can't be sent