Custom Domain Publishing Does Non Purpose Post Feed Redirect
Friday, October 11, 2019
Edit
One of the benefits of custom domain publishing, for a properly setup domain, is that the BlogSpot URL is automatically redirected to the domain.
Not all weblog owners realise that the BlogSpot to domain URL redirect includes the weblog feed - 1 time the Transition period ends, in addition to the weblog is republished to the domain.
Some weblog owners intend that the Post Feed Redirect setting needs to live on used when re publishing their weblog to a custom domain. This is non true, however. Use of the custom domain redirect, addition the post feed redirect, tin solely number inwards 1 of 2 problems.
The Post Feed Redirect setting is used to redirect feed references, to a separately existing feed file.
The Post Feed Redirect is non used where it is non needed - in addition to amongst a weblog published to a properly setup custom domain, it's non needed.
Let's await at an HTTP trace, showing the weblog feed for a custom domain published blog, that uses a post feed redirect - inwards this case, nosotros stimulate got the feed for "mybloggerblog.blogspot.com" redirected to "mybloggerblog.com".
Start amongst the BlogSpot based feed URL, for "mybloggerblog.blogspot.com".
With a properly setup custom domain, in addition to no PFR setting used, the adjacent display would live on the XML file, for the feed. Here, the PFR was develop to "http://mybloggerblog.com/".
Now, nosotros are looking at a typical custom domain rootage to "www" alias redirect.
And now, nosotros are looking at the formatted weblog contents - non the newsfeed.
Unfortunately, the weblog itself is non a proper XML file (required for a feed), it's HTML / XML.
And if the feed customer is, for instance, a dynamic template, the would live on reader is looking at the former spinning gears. Until he gets bored, closes the browser, in addition to emails you
If you lot stimulate got made this mistake, merely clear the Post Feed Redirect.
Not all weblog owners realise that the BlogSpot to domain URL redirect includes the weblog feed - 1 time the Transition period ends, in addition to the weblog is republished to the domain.
Some weblog owners intend that the Post Feed Redirect setting needs to live on used when re publishing their weblog to a custom domain. This is non true, however. Use of the custom domain redirect, addition the post feed redirect, tin solely number inwards 1 of 2 problems.
- A feed redirect loop.
- A feed URL that points to invalid content.
The Post Feed Redirect setting is used to redirect feed references, to a separately existing feed file.
The Post Feed Redirect is non used where it is non needed - in addition to amongst a weblog published to a properly setup custom domain, it's non needed.
Let's await at an HTTP trace, showing the weblog feed for a custom domain published blog, that uses a post feed redirect - inwards this case, nosotros stimulate got the feed for "mybloggerblog.blogspot.com" redirected to "mybloggerblog.com".
Start amongst the BlogSpot based feed URL, for "mybloggerblog.blogspot.com".
Sending request:
GET /feeds/posts/default HTTP/1.1Host: mybloggerblog.blogspot.comUser-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.224.106
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:HTTP/1.1·301·Moved·Permanently(CR)(LF)Content-Type:·text/html;·charset=UTF-8(CR)(LF)Location:·http://www.mybloggerblog.com/feeds/posts/default(CR)(LF)
With a properly setup custom domain, in addition to no PFR setting used, the adjacent display would live on the XML file, for the feed. Here, the PFR was develop to "http://mybloggerblog.com/".
Sending request:
GET /feeds/posts/default HTTP/1.1Host: www.mybloggerblog.comUser-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.127.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:HTTP/1.1·302·Moved·Temporarily(CR)(LF)Location:·http://mybloggerblog.com/(CR)(LF)
Now, nosotros are looking at a typical custom domain rootage to "www" alias redirect.
Sending request:
GET / HTTP/1.1Host: mybloggerblog.comUser-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 216.239.32.21
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:HTTP/1.1·301·Moved·Permanently(CR)(LF)Location:·http://www.mybloggerblog.com/(CR)(LF)
And now, nosotros are looking at the formatted weblog contents - non the newsfeed.
Sending request:
GET / HTTP/1.1Host: www.mybloggerblog.comUser-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.127.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:HTTP/1.1·200·OK(CR)(LF)
Unfortunately, the weblog itself is non a proper XML file (required for a feed), it's HTML / XML.
<!DOCTYPE·html·PUBLIC·"-//W3C//DTD·XHTML·1.0·Strict//EN"·"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">(LF)<html·dir='ltr'·xmlns='http://www.w3.org/1999/xhtml'·xmlns:b='http://www.google.com/2005/gml/b'·xmlns:data='http://www.google.com/2005/gml/data'·xmlns:expr='http://www.google.com/2005/gml/expr'>(LF)<head>(LF)
...
<link·href='http://www.mybloggerblog.com/'·rel='canonical'/>(LF)
<link·rel="alternate"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default?alt=rss"·/>(LF)
<link·rel="service.post"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/feeds/2302596229887627781/posts/default"·/>(LF)
<link·rel="EditURI"·type="application/rsd+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/rsd.g?blogID=2302596229887627781"·/>(LF)
<link·rel="me"·href="http://www.blogger.com/profile/12619425977406185402"·/>(LF)
<link·rel="openid.server"·href="http://www.blogger.com/openid-server.g"·/>(LF)
<link·rel="openid.delegate"·href="http://www.mybloggerblog.com/"·/>(LF)
And if the feed customer is, for instance, a dynamic template, the would live on reader is looking at the former spinning gears. Until he gets bored, closes the browser, in addition to emails you
Your weblog is downwards - again.
If you lot stimulate got made this mistake, merely clear the Post Feed Redirect.