Http redirect on subdomain

Support
,
6

Hi, @AG-Labs. I see the redirect when I test:

$ curl -svo /dev/null http://poker.ag-labs.io/
*   Trying 167.172.221.254...
* TCP_NODELAY set
* Connected to poker.ag-labs.io (167.172.221.254) port 80 (#0)
> GET / HTTP/1.1
> Host: poker.ag-labs.io
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Cache-Control: public, max-age=0, must-revalidate
< Content-Length: 41
< Content-Type: text/plain
< Date: Tue, 08 Sep 2020 08:15:06 GMT
< Location: https://poker.ag-labs.io/
< Age: 0
< Connection: keep-alive
< Server: Netlify
< X-NF-Request-ID: 3918bb66-571e-4b9f-894f-6b61341ad058-242712
<
{ [41 bytes data]
* Connection #0 to host poker.ag-labs.io left intact
* Closing connection 0

If you are still seeing failing redirects, we need to be able to track the HTTP response with this issue. The simplest way to do this is to send us the x-nf-request-id header which we send with every HTTP response.

There more information about this header here:

If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:

  • the complete URL requested
  • the IP address for the system making the request
  • the IP address for the CDN node that responded
  • the day of the request
  • the time of the request
  • the timezone the time is in