Re^2: Is LWP::Simple's get function caching pages?

You're right about the browser behaving the same way, but reloading the page solved it. I would have supposed that to be a sign that the browser caches the page, not the server. I don't think that LWP::Simple inherits browser settings, though. That leaves me with my ISP possibly caching pages, although I can't figure why a reload would solve the problem in this case.
And I definitely can't change the page itself (it's Yahoo's weather service - and yes, I checked: the terms of service don't seem to forbid the collection of weather data).
Thanks for your help.
CombatSquirrel.

Entropy is the tendency of everything going to hell.

Comment on Re^2: Is LWP::Simple's get function caching pages?

Replies are listed 'Best First'.
Re^3: Is LWP::Simple's get function caching pages? by bart (Canon) on Sep 18, 2004 at 08:34 UTC
No, force-reloading the page probably sent along extra headers to the webserver, telling it to reread the file. Now, if you can figure out what those headers are, you can duplicate that behaviour with LWP, though you're probably will have to use something slightly more powerful (= lower level) than LWP::Simple.	[reply]
Re^4: Is LWP::Simple's get function caching pages? by CombatSquirrel (Hermit) on Sep 18, 2004 at 10:10 UTC
I thought about requesting the file twice, which might look to the server as if I were reloading the file. The problem resolved magically, though (maybe because it's daytime now and more people are accessing the page) and I'll just leave it with that for now (I'll see whether the problem reappears tonight). Thanks for your responses. CombatSquirrel. Entropy is the tendency of everything going to hell.	[reply]