Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#28247 closed defect (bug) (invalid) feed guids are cached without regard to protocol

Reported by: drmaciver's profile DRMacIver Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.0
Component: Feeds Keywords:
Focuses: Cc:


I'm unclear if this is a bug specific to the deployment or whether it's a general issue. I don't have a non blog which responds to both http and https to test this on, and I've not investigated the code for this.

In short the issue is this:

Wordpress feed entries have their guid field calculated based on the protocol. i.e. a guid is something like http/ If I request I'll get https guids, if I request I'll get http guids.

The problem is that this is cached for a period of time, and the cache key ignores the protocol. This means that if I request, get https guids, and then immediately request then I will get https guids in the http feed. This will continue to be the case until the cache expires and the new feed is calculated with the appropriate guids.

Change History (2)

#1 @johnbillion
10 years ago

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

Thanks for the report David.

This is an issue due to the caching in place on That said, the issue can also be seen in feeds on the site which, as far as I know, runs on the infrastructure.

This is the same issue as #406 on our meta issue tracker. Evidently this is something that needs to be passed onto the team.

I'm going to close this as invalid as it doesn't directly relate to the WordPress software. Feel free to keep an eye on meta #406.

#2 @johnbillion
10 years ago

Just so you know, this has now been fixed.

Note: See TracTickets for help on using tickets.