Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-184

Host header/cache lookup entry doesn't match remap.config perfectly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 2.0.0a
    • Core
    • None

    Description

      If I had this in my remap.config

      map http://a.com http://b.com:80

      The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config

      Attachments

        1. port-80.patch
          2 kB
          Manjesh Nilange
        2. port-80.patch
          2 kB
          Manjesh Nilange

        Issue Links

          Activity

            People

              zwoop Leif Hedstrom
              manjesh Manjesh Nilange
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: