Incorrect HTTP Content-Type header for binary artifacts

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Using the default Winstone Servlet Engine, Hudson returns a HTTP Content-Type
      header of "text/html;charset=UTF-8" for all files. This causes a problem when
      downloading binary artifacts from either archived artifacts or the workspace:
      the browser displays the files' contents inline instead of prompting a Save As
      dialog. (This occurs on Firefox 2.0, but not IE7.)

      Ideally, the MIME type of the artifacts should be auto-detected, and set within
      the Content-Type header.

            Assignee:
            Unassigned
            Reporter:
            kianwin
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: