-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Sitemap does not include HTTPS links for custom domains #5445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still valid bot. |
Marking the issue as Accepted since is something we want to fix. |
hello @humitos i would like take this issue up what exactly do i need to do for this ??? |
Hi @KartikKapil! The requirements for this issue are in the description of the issue. Is there any particular point that you don't understand from there? |
@humitos i could not figure out that how to change the function" get_docs_url" to make sure it points to the pages but does not redirect |
Hey @humitos I would like to work on this issue. Is it still open? |
@ashadhaz yes, it's still open |
@ashadhaz are you still working on this issue? If not I would like to work on this. |
I am working on this issue as mentioned on IRC. @stsewd how should this be fixed, there are two approaches:
|
This is now fixed 👍 |
The generated
sitemap.xml
gets the URL for each available version by callingget_docs_url
. For custom domains, this returns HTTP links, which perform a 301 redirect to the HTTPS version. But sitemaps should only point to actual pages (references: Google, Bing) and not redirects, or the crawler may begin losing trust in the sitemap and put a penalty on the information it contains.Also, the docstring for this method is probably incorrect, as noted here. This method actually returns HTTPS links for non-custom domains. Related issue: #4641
Example: https://docs.dash.org/sitemap.xml
The text was updated successfully, but these errors were encountered: