|
I don't know the solution to the following problem, so I thought I just ask you  :
When I use Safari to work with a PyDS installation, everything works fine if it is my local machine with my local PyDS. It does work fine when accessing a PyDS on my work machine that's hidden behind two cascaded ProxyPass-Apache-VirtualServers (just virtual servers that pull their content via non-caching proxypass directives from a machine behind them).
It doesn't work fine when I access a PyDS installation at simon.bofh.ms - my main private webserver. The weird thing: the setup isn't actually really problematic, it's just a PyDS running on a different machine. No cache in between. No special hacks working. Just two machines, one the browser, the other the PyDS instance.
What happens is the following: from time to time I don't get the current content of a page, but an old one - even though pages are marked as Pragma: no-cache and the browser does say it doesn't cache them. But I still get those that old content. Most often this happens in the aggregator - I purge a feed and still see that feed listed in the channel overview, even though it's already empty (and a reload shows that it is empty).
This only happens with Safari and the new Omniweb (using the same WebKit as Safari), so I assume it must have something to do with Safari itself. But I absolutely don't understand what is going on ...
If I use Firebird instead of Safari, everything works.
Update: I just put my PyDS with the problem behind an Apache server, so it is used mostly like the one at work. The weird thing: while the one at work works fine, the one with the problem still has the problem. It caches, although there is no caching allowed and needed. Werid.
Another update: when changing the redirecting that's taking place from the intermediate HTML page to direct Location headers and 302 errors, the problem with Safari disapears. This is really weird stuff, but since it's gone for now, I don't really care that much 
|
