Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-2148

Add the ability to disable Filename encoding in Content-Disposition

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 3.6.3.Final, 4.0.0.CR1
    • 3.6.1.Final, 3.6.2.Final, 4.0.0.Beta7
    • jaxrs
    • None

    Description

      A change was introduced for RESTEASY-2046 to encode non-US-ASCII filenames per RFC 5987, but the fix was incorrect/incomplete.
      Also latest RFC for multipart messages inside HTTP is defined in RFC-7578 and there is stated:

      • NOTE: The encoding method described in RFC5987, which would add a "filename*" parameter to the Content-Disposition header field, MUST NOT be used.

      Commons FileUpload library cannot consume file correctly if filename is like filename*=utf-8''Test%20file.pdf
      Therefore, please add into method MultipartFormDataOutput.addFormData(String key, Object entity, MediaType mediaType, String filename) the parameter that will disable filename encoding

      Attachments

        Issue Links

          Activity

            People

              rhn-support-asoldano Alessio Soldano
              tolikbest61_jira Anatolii Gurskyi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: