feat: add rss link to document head for autodiscovery - #416
Merged
Conversation
In order to not end up with a double slash in the path when constructing the absolute feed url out of `.Site.BaseURL` and `.Site.Params.news.feed`, I've inserted a dot in-between. In a http request, double slashes will be transmitted as-is, potentially causing issues, whereas dot segments are to be resolved by the client beforehand (as per rfc3986). It's the little things… ;-))
Member
|
Cool, thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With this link, a rss reader can be pointed to any url of the site and it will find the feed.
(In order to not end up with a double slash in the path when constructing the absolute feed url out of
.Site.BaseURLand.Site.Params.news.feed, I've inserted a dot in-between. In a http request, double slashes will be transmitted as-is, potentially causing issues, whereas dot segments are to be resolved by the client beforehand (as per rfc3986). It's the little things… :-))