Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-627

Incorrect HTTP Content-Type header for binary artifacts

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      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.

          [JENKINS-627] Incorrect HTTP Content-Type header for binary artifacts

          kianwin created issue -

          Fixed in 1.115.

          Kohsuke Kawaguchi added a comment - Fixed in 1.115.
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          kianwin added a comment -

          Wow, that was light speed!

          Is the fix contained within build 3376?

          kianwin added a comment - Wow, that was light speed! Is the fix contained within build 3376?

          kianwin added a comment -

          Works in 1.115. =)

          kianwin added a comment - Works in 1.115. =)
          kianwin made changes -
          Status Original: Resolved [ 5 ] New: Verified [ 10000 ]
          Richard Bywater made changes -
          Status Original: Verified [ 10000 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: gui [ 15492 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 130700 ] New: JNJira + In-Review [ 200045 ]

            Unassigned Unassigned
            kianwin kianwin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: