http://bugs.gpodder.org/show_bug.cgi?id=210





--- Comment #5 from [EMAIL PROTECTED]  2008-10-06 07:06:35 ---
> Please post the output of "gpodder --verbose", i.e. with the command
> 
> gpodder --verbose 2>&1 | tee ~/Desktop/gpodder-debug.log

I have attached the log file. The scenario is the following:

1- I start gpodder
2- The feeds are automatically updated on startup: note that two new episodes
are found i.e:

[   5.653] Episode added: LE MASQUE ET LA PLUME 05.10.2008
[   7.144] Episode added: LES PETITS BATEAUX 05.10.2008

but note also that:

[   4.352] Channel http://radiofrance-podcast.net/podcast/rss_10060.xml is up
to date

3- The new episodes are downloaded.

4- I open http://radiofrance-podcast.net/podcast/rss_10060.xml with a web
browser and get the old version. I then click on the "Reload" button of the web
browser and get the new version of the XML file.

5- I click on "Check for Updates" in gpodder: 

[ 307.221] Updating channels....

Note now that

[ 309.211] Episode added: LE JOURNAL DE 18H 05.10.2008

Although it is not clear from the log file, this new episode corresponds to the
new version of http://radiofrance-podcast.net/podcast/rss_10060.xml...

6- This new episode is downloaded.

> Are you using a proxy, or maybe is your company/ISP using a transparent proxy
> that does the caching?

I am not using a proxy, maybe my ISP is, or someone in between the
http://radiofrance-podcast.net and my machine is, who knows?? 

> It doesn't look like a gPodder problem to me.

I don't agree with that. If my web browser is able to get the most recent
version of the XML file (irrespective of proxies or whatever), so should
gpodder. For example if I do the scenario above but omit step 4 (i.e. I ask
gpodder to check for new feeds twice), it still doesn't see the new file. It
should (even if you could argue that somebody somewhere along the chain should
have configured things better).

thanks for your help

Stephane


-- 
Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs

Reply via email to