Make WordPress Core

Opened 8 years ago

Closed 7 years ago

#37497 closed defect (bug) (invalid)

Permalink does not contain https and this causes HTTP Error 301 on all feeds

Reported by: peprdotcom's profile peprdotcom Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.5.3
Component: Feeds Keywords: https close
Focuses: Cc:


We could not get Bloglovin to work with the feed It turned out that while the whole blog was using https and also in the settings, content inside the feed wasn't . We found this by checking the feed validity:
Result: Server returned HTTP Error 301: The HTTP server returned a redirect error that would lead to an infinite loop. The last 30x error message was: Moved Permanently

When looking at the feed we immediately found that all links where not using https:

	<title>A Green Coconut</title>
	<atom:link href="" rel="self" type="application/rss+xml" />
	<description>Pura Vida</description>
	<lastBuildDate>Sat, 23 Jul 2016 01:22:50 +0000</lastBuildDate>
		<title>Nooit meer haast</title>

WordPress-adres (URL):
Siteadres (URL):

We tried to fix this with "WordPress HTTPS" plug-in but no results.

It turns out that several parts of the feed contain errors. The atom:link, item link, guid link.

What can we do to fix this? It appears that some parts work but most don't. Help is appreciated.

Change History (4)

#1 @SergeyBiryukov
8 years ago

  • Component changed from Permalinks to Feeds

#2 @johnbillion
8 years ago

  • Keywords https added

#3 @stevenkword
8 years ago

I'm having trouble replicating this for the atom:link and item link elements.

I am seeing this for the GUID, but technically, this doesn't require the protocol at all to be valid.

Last edited 8 years ago by stevenkword (previous) (diff)

#4 @stevenkword
7 years ago

  • Keywords close added
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

I'm closing this as "invalid" since I am not able to replicate the problem. The original reporter's feed also is not showing the reported problem currently, indicating that the problem might have been site-specific and has since been resolved.

Note: See TracTickets for help on using tickets.