[wp-trac] [WordPress Trac] #28247: wordpress.com feed guids are cached without regard to protocol
WordPress Trac
noreply at wordpress.org
Wed May 14 20:26:29 UTC 2014
#28247: wordpress.com feed guids are cached without regard to protocol
--------------------------+-----------------------------
Reporter: DRMacIver | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Feeds | Version: trunk
Severity: normal | Keywords:
Focuses: |
--------------------------+-----------------------------
I'm unclear if this is a bug specific to the wordpress.com deployment or
whether it's a general issue. I don't have a non wordpress.com 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/https://drmaciver.wordpress.com?p=blah. If I request
https://drmaciver.wordpress.com/feed I'll get https guids, if I request
http://drmaciver.wordpress.com/feed 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
https://drmaciver.wordpress.com/feed, get https guids, and then
immediately request http://drmaciver.wordpress.com/feed 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.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28247>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list