{"issue":{"title":"DTS infinite loop edge case","user":{"login":"Trott","id":718899,"url":"https://api.github.com/users/Trott","avatar_url":"https://secure.gravatar.com/avatar/d9bebc8f32aaad1275a931e2045196e0?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d9bebc8f32aaad1275a931e2045196e0"},"created_at":"2011-12-22T18:21:30Z","milestone":{"open_issues":1,"title":"1.2.10","created_at":"2011-12-22T18:43:22Z","creator":{"login":"Trott","id":718899,"url":"https://api.github.com/users/Trott","avatar_url":"https://secure.gravatar.com/avatar/d9bebc8f32aaad1275a931e2045196e0?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d9bebc8f32aaad1275a931e2045196e0"},"state":"open","due_on":null,"closed_issues":2,"number":5,"description":null,"url":"https://api.github.com/repos/ucla/mwf/milestones/5"},"labels":[],"state":"open","updated_at":"2011-12-26T19:34:08Z","id":2640020,"closed_at":null,"html_url":"https://github.com/ucla/mwf/issues/45","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Set up a server called, say, login.proxy.library.ucla.edu.\r\n\r\nServe up a page in docroot called, say, menu.htm.\r\n\r\nAssume that the end user might access it through HTTPS or might access it through HTTP, so you have code like this:\r\n\r\n    <link rel=\"stylesheet\" type=\"text/css\" href=\"//p1.m.ucla.edu/assets/css.php\" media=\"screen\">\r\n    <script type=\"text/javascript\" src=\"//p1.m.ucla.edu/assets/js.php\"></script>\r\n    <meta name=\"viewport\" content=\"height=device-height,width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=no;\">\r\n\r\n(Sure, they shouldn't use p1.m.ucla.edu, but the point is that they use a name that isn't m.ucla.edu. Certainly, there are use cases where more than one hostname for the mobile site is desirable.  This is especially true if we want to extract DTS from MWF and make it available for general use.  Anyway, even if they shouldn't do this for other reasons, it should not result in an infinite redirect loop.)  \r\n\r\nAssume m.ucla.edu is running MWF 1.2.09.\r\n\r\nBecause of the different p1.m.ucla.edu vs. m.ucla.edu hostnames, `vars.php` will alternately see and not see the m.ucla.edu cookies (depending on if it is being pulled in via http://login.proxy.library.ucla.edu/menu.htm or via http://m.ucla.edu/assets/passthru.php).  \r\n\r\nThe end result is an infinite redirect loop.\r\n\r\n","number":45,"url":"https://api.github.com/repos/ucla/mwf/issues/45","comments":15,"assignee":{"login":"ebollens","id":761092,"url":"https://api.github.com/users/ebollens","avatar_url":"https://secure.gravatar.com/avatar/3bb00bb9eda3eca8b98a01756a392346?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3bb00bb9eda3eca8b98a01756a392346"}},"comment":{"user":{"login":"ebollens","id":761092,"url":"https://api.github.com/users/ebollens","avatar_url":"https://secure.gravatar.com/avatar/3bb00bb9eda3eca8b98a01756a392346?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3bb00bb9eda3eca8b98a01756a392346"},"created_at":"2011-12-26T19:34:08Z","updated_at":"2011-12-26T19:34:08Z","id":3276422,"body":"My concern is that the framework may be made available under a different port and not 80/443.\r\n\r\nUnder this approach, ```getservbyname()``` would return 80/443, but those don't need to be specified in the URI anyways. The challenge instead arrises when a different port is specified. However, when I adjusted the Listen to include a port number and check ```HTTP_HOST```, it actually seems to reflect this port number as part of the name, \"resolving\" the problem itself.","url":"https://api.github.com/repos/ucla/mwf/issues/comments/3276422"},"action":"created"}