#81 HTTP 302 redirects aren't followed

2.3.0
closed-invalid
nobody
Parsing (9)
5
2008-10-01
2008-09-28
showdax
No

If I add a feed that has an HTTP 302 redirect, Vienna doesn't follow it, and just assumes it's an empty feed (the message body is empty).

Here's an example: http://feeds.pitchforkmedia.com/pitchfork/today. It redirects to http://feedproxy.google.com/pitchfork/today.

Discussion

  • Steve Palmer
    Steve Palmer
    2008-09-28

    I can reproduce this. It works fine with Safari. Vienna is clearly picking up the redirect but not getting the data from the feed. Needs investigation.

     
  • Steve Palmer
    Steve Palmer
    2008-09-28

    • labels: --> Parsing
    • milestone: --> 2.3.0
     
  • Jeff Johnson
    Jeff Johnson
    2008-09-28

    Sorry, I typo, I meant to say "I can't reproduce."

     
  • showdax
    showdax
    2008-09-28

    Actually, I can't reproduce myself now. Maybe it's not just the redirect, but I had been subscribed to the feed via the original URL for months, and at some point Vienna stopped getting any new articles from it. I assume this must've been around the time they put up the 302 redirect.

    Or it could be totally unrelated. I'm not sure how to reproduce the issue now, as I've since recreated the feed in Vienna.

     
  • showdax
    showdax
    2008-09-28

    Also, I'm using Mac OS X 10.5.5. I'm also using the current developer preview of Safari 4.0 (5528.1). Safari displays the feed just fine.

     
  • Steve Palmer
    Steve Palmer
    2008-09-28

    Interesting. The first time I tried this, Vienna just hung trying to load that feed. The activity log just showed the connect and the redirect. I was able to pull it down in Safari and wget. However it works in the debugger and it worked subsequently outside the debugger. This is with 10.5.5.

    showdax - is this consistently reproducible? Also, which version of Vienna?

     
  • showdax
    showdax
    2008-09-28

    I'm using the current stable version, 2.3.0.2300. I still haven't been able to reproduce it.

    The feed also supports If-Modified-Since and If-None-Match, which could be at play. I could imagine that it got the HTTP headers but not the full message body, but still cached the request. I don't think that's the case though, considering Vienna stopped getting articles from the feed about two months ago.

     
  • showdax
    showdax
    2008-10-01

    Upon further inspection, it looks like the feed isn't handling If-Modified-Since correctly. You can close this bug.

     
  • Jeff Johnson
    Jeff Johnson
    2008-10-01

    Closing

     
  • Jeff Johnson
    Jeff Johnson
    2008-10-01

    • status: open --> closed-invalid