HAProxy 301 redirect [#2649982]

At the HAProxy level there is a 301 redirect to add a slash at the end of the url.
The issue is HAProxy is not aware of the url that made the request in the first place, so it runs the 301 redirect for what it knows.

This is an edge case and requires a user to make a specific action. And will be a moot point if/when we move to Fastly as the load balancer

If we decide to fix this, it is probably easiest to do at the Fastly level.

Comments

Comment #1

14 January 2016 at 05:15

isntall created an issue. See original summary.

Comment #2

isntall CreditAttribution: isntall at Drupal Association commented 14 January 2016 at 05:18

At the moment it looks like there might be miss configuration with the difference between
https://ftp.drupal.org/files
and
https://ftp.drupal.org/files/

Here are the curl out puts

$ curl -I https://ftp.drupal.org/files/
HTTP/1.1 200 OK
Server: nginx/1.8.0
Content-Type: text/html
Last-Modified: Thu, 05 Feb 2015 04:19:54 GMT
ETag: "54d2ef6a-208"
Via: 1.1 varnish
Fastly-Debug-Digest: 614969074c20f2e88c81c58f1991eedcc49b29f11ebfa3df5810c2a7cabb188b
Content-Length: 520
Accept-Ranges: bytes
Date: Thu, 14 Jan 2016 07:24:22 GMT
Via: 1.1 varnish
Age: 7864
Connection: keep-alive
X-Served-By: cache-sea1924-SEA, cache-lax1427-LAX
X-Cache: HIT, MISS
X-Cache-Hits: 1, 0
Vary: Accept-Encoding

$ curl -I https://ftp.drupal.org/files                                       
HTTP/1.1 301 Moved Permanently
Server: nginx/1.8.0
Content-Type: text/html
Location: http://ftp-origin.drupal.org/files/
Via: 1.1 varnish
Fastly-Debug-Digest: 63fd8e187a8afe7f2d3bbac110b7d5e999998c55691f00b7d7f6bb41c1260af9
Content-Length: 184
Accept-Ranges: bytes
Date: Thu, 14 Jan 2016 03:39:46 GMT
Via: 1.1 varnish
Age: 69602
Connection: keep-alive
X-Served-By: cache-sea1926-SEA, cache-sjc3130-SJC
X-Cache: HIT, MISS
X-Cache-Hits: 1, 0