Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-5686

Content type guessing for external embedded resources doesn't use the Content-type HTTP header

XMLWordPrintable

      Example:

      Returns a JPEG image with the headers:

      HTTP/1.1 200 OK
      Date: Wed, 08 Mar 2006 18:11:12 GMT
      Server: Apache/2.2.0 (Unix)
      Connection: close
      Content-Length: 37534
      Content-Type: image/jpeg

      The embedded resource parser incorrectly guesses the content type as 'application/octet-stream' based on the filename 'preview'. Confluence is then unable to render it.

      When the filename guessing provides no useful content type for external resources, the parser should check the content-type HTTP header.

            [CONFSERVER-5686] Content type guessing for external embedded resources doesn't use the Content-type HTTP header

            No work has yet been logged on this issue.

              Unassigned Unassigned
              matt@atlassian.com Matt Ryall
              Affected customers:
              1 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: