≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #1333

Bug #1333: Duplicate entries in Atom feeds

Kind bug
Product wincent.dev
When 2009-06-26T04:48:29Z
Status closed
Reporter Greg Hurrell
Tags no tags

Description

Sho Fukamachi reports seeing duplicate entries in Atom feeds for the site, and has done some detective work too:

I waited until the phenomenon recurred, then grabbed another copy of the RSS feed. I chose an article which appeared in duplicate and diffed its entries in the old and new files.

I needn't have bothered; the problem is plain as day and would have revealed itself if i'd looked properly.

And this is my reply:

So if someone accesses the site via the rails subdomain and is the first to view the feed since the last time the cache was cleared, "rails" will be used in all the entries.

And if someone accesses the site via wincent.dev and is the first to view the feed since the last time the cache was cleared, "wincent.dev" will be used.

So that explains everything. One of the unexpected consequences of providing two different URLs to access the same application. Doh.

Bugger.

I think I'm going to apply some nginx redirection magic to force all accesses. Unless you have a better suggestion.

Thanks for your astute trouble-shooting.

Comments

  1. Greg Hurrell 2009-06-26T04:59:13Z

    See also ticket #1270: I've actually wanted to make this move for some time, but it was not until this feed issue was brought to my attention that the matter has become urgent. (Ticket #1270 is really describing a minor annoyance/glitch, but the duplicate feed entry issue is an out and out bug.)

  2. Greg Hurrell 2009-06-26T05:15:32Z

    Ok, the redirect is now set up. See ticket #1270 for a few more details. Will mark as closed.

  3. Greg Hurrell 2009-06-26T05:15:36Z

    Status changed:

    • From: open
    • To: closed
Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets