#28247 closed defect (bug) (invalid)
wordpress.com feed guids are cached without regard to protocol
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 4.0 |
| Component: | Feeds | Keywords: | |
| Focuses: | Cc: |
Description
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.
Thanks for the report David.
This is an issue due to the caching in place on wordpress.com. That said, the issue can also be seen in feeds on the wordpress.org site which, as far as I know, runs on the wordpress.com infrastructure.
This is the same issue as #406 on our meta issue tracker. Evidently this is something that needs to be passed onto the wordpress.com 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.