Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3452

Content-type of a rendered page should not be a function of the request

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Obsolete
    • Icon: Neutral Neutral
    • None
    • 4.4.1
    • templating
    • None

      The Content-Type response header is currently a direct function of the extension in the request.
      This is not good for several reasons (security, seo, ...)
      The Content-Type should simply be a function of whatever renders the content

      Example: http://demopublic.magnolia-cms.com/demo-project/about.jpeg yields:

      Request URL:http://demopublic.magnolia-cms.com/demo-project/about.jpeg
Request Method:GET
Status Code:200 OK
Request Headers
Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent:Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_5; en-us) AppleWebKit/533.18.1 (KHTML, like Gecko) Version/5.0.2 Safari/533.18.5
Response Headers
Cache-Control:max-age=900
Connection:Keep-Alive
Content-Length:16305
Content-Type:image/jpeg;charset=UTF-8
Date:Tue, 07 Dec 2010 09:54:07 GMT
Keep-Alive:timeout=15, max=97
Last-Modified:Tue, 07 Dec 2010 09:54:07 GMT
Server:Apache/2.2.14 (Ubuntu)
X-Magnolia-Registration:Registered

        Acceptance criteria

              Unassigned Unassigned
              gjoseph Magnolia International
              Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD