ERROR: Fetching the page failed because it resulted in too many redirects

cards

#1

Issue:

I’m having troubles validating a card for a url that returns a 301.

The card for the www name works fine but when I try to validate for the one without www I get this error

ERROR: Fetching the page failed because it resulted in too many redirects.

I’ve checked and curl is able to get it using TwitterBot agent:

curl -v -L -A Twitterbot macrosfirst.com
* Rebuilt URL to: macrosfirst.com/
*   Trying 50.63.202.10...
* TCP_NODELAY set
* Connected to macrosfirst.com (50.63.202.10) port 80 (#0)
> GET / HTTP/1.1
> Host: macrosfirst.com
> User-Agent: Twitterbot
> Accept: */*
>
< HTTP/1.1 302 Found
< Connection: close
< Pragma: no-cache
< cache-control: no-cache
< Location: /
<
* Curl_http_done: called premature == 0
* Closing connection 0
* Issue another request to this URL: 'http://macrosfirst.com/'
* Hostname macrosfirst.com was found in DNS cache
*   Trying 50.63.202.10...
* TCP_NODELAY set
* Connected to macrosfirst.com (50.63.202.10) port 80 (#1)
> GET / HTTP/1.1
> Host: macrosfirst.com
> User-Agent: Twitterbot
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Cache-Control: max-age=900
< Content-Type: text/html
< Location: http://www.macrosfirst.com
< Server: Microsoft-IIS/7.5
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< Date: Sun, 09 Jul 2017 03:19:32 GMT
< Content-Length: 0
< Age: 1
< Connection: keep-alive
<
* Curl_http_done: called premature == 0
* Connection #1 to host macrosfirst.com left intact
* Issue another request to this URL: 'http://www.macrosfirst.com'
* Rebuilt URL to: http://www.macrosfirst.com/
*   Trying 52.219.88.68...
* TCP_NODELAY set
* Connected to www.macrosfirst.com (52.219.88.68) port 80 (#2)
> GET / HTTP/1.1
> Host: www.macrosfirst.com
> User-Agent: Twitterbot
> Accept: */*
>
< HTTP/1.1 200 OK

So apparently 2 redirects are too many ? Is there a way of fixing this error ?


#2

I’m not seeing this error, the card seems to work fine without the www prefix.


#3

Are you sure ? I’m still seeing the same error:


#4

Weird. Yes I can confirm that I am seeing that URL work in the validator from here.


#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.