[
https://issues.apache.org/jira/browse/TS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641292#comment-14641292
]
Thomas Jackson commented on TS-3141:
------------------------------------
Even in the event that I do own the origin-- how am I supposed to configure it?
If I have an app which handles requests on /foo on a.com and b.com, if I
disable pristine host headers on the origin it will see a request for
foo-hostname.somedomain.com/foo -- and would then be unable to distinguish
between a.com and b.com requests. I could potentially set a different header
(Not Host) to the contents of the host header but that is (1) very confusing...
and (2) would have the same content anyways (incorrect port?).
> Port number in host header breaks ATS remap
> -------------------------------------------
>
> Key: TS-3141
> URL: https://issues.apache.org/jira/browse/TS-3141
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Brian Geffon
> Labels: newbie
> Fix For: 6.1.0
>
>
> If someone adds port 80 (lets say) to the host header of a request, ATS remap
> fails
> {code}
> [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:80'
> https://www.ogre.com
> HTTP/1.1 404 Not Found on Accelerator
> Date: Thu, 16 Oct 2014 21:14:02 GMT
> Connection: keep-alive
> Via: https/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [c s f ])
> Server: ATS/5.2.0
> Cache-Control: no-store
> Content-Type: text/html
> Content-Language: en
> Content-Length: 297
> {code}
> Although if you set the port to 443 it seems to work fine
> {code}
> [thjackso@thjackso-ld ~]$ curl -I -4k -H 'Host: www.ogre.com:443'
> https://www.ogre.com
> HTTP/1.1 200 OK
> Date: Thu, 16 Oct 2014 21:15:09 GMT
> Server: ATS/5.2.0
> X-Drupal-Cache: MISS
> Expires: Sun, 19 Nov 1978 05:00:00 GMT
> Last-Modified: Thu, 16 Oct 2014 21:15:09 +0000
> Cache-Control: public, max-age=300
> Content-Language: en
> X-Generator: Drupal 7 (http://drupal.org)
> Vary: Cookie
> Content-Type: text/html; charset=utf-8
> Age: 0
> Connection: keep-alive
> Via: http/1.1 cosmo.ogre.com (ApacheTrafficServer/5.2.0 [cMsSf ])
> {code}
> In addition I can send a host header with 443 on the http port and I'll get
> similar behavior. This leads me to believe that if you set the port to
> anything that isn't the default for the schema you are connecting on it fails
> remap (url looks like https:/// in the logs).
> I would think that the port in the host header would be completely
> ignored.... right?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
