Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-18429

Content redirection through URL Aliases (HTTP 301) - response compliance with RFC 2616

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Medium Medium
    • None
    • 4.4.0
    • Misc
    • None
    • Operating System: Any
      PHP Version: Any
      Database and version: Any
      Browser (and version): Any (Though firefox with firebug helps investigating this issue)

    Description

      URL aliases created through URL translator, with redirection to destination ticked, generates a HTTP header not fully compliant with RFC 2616.

      According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 HTTP/1.1 Status Code Definitions, Location header should assume the absolute URL to the page. Currently it presents the relative URI.

      Steps to reproduce

      Create an URL Alias through URL translator option in Admin Portal
      . Make sure "Alias should redirect to its destination" checkbox is ticked.
      Open the new alias Front End
      . Examine the HTTP headers of this page. Location header's value assumes the relative URI of the page instead of the absolute URL.

      Attachments

        Activity

          People

            jv@ez.no jv@ez.no
            joc@ez.no joc@ez.no
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: