I was having an error for the longest time with the viewRssBox on
the right of my Radio site, but until now couldn't be bothered to look
at it. I was actually taking out the blogroll but commented the wrong
thing by mistake. In the debugging process I discovered a weird
interaction with caching and 301 URLs.
An HTTP asside: 301 is the HTTP numeric response for
"Permanently Moved". It is an indication that you should never
use this URL in the future but instead always go directly to the
refered URL. I had been refering to my LiveJournal RSS as
"htttp://username.livejournal.com", which will 301 to
"http://www.livejournal.com/users/username/data/rss".
In Radio Userland, xml.rss.readService caches the RSS that it reads
as a table at @user.xml.rss.cache.[url]. Somewhere along the line
there's confusion about that URL as the 301 changes it from one to the
other. What I think is happening is that in xml.rss.readService where
redirectInfo is checked the table.rename to the new URL fails because
the table from the last time in still there in the cache. readService
probably worked the first time and only failed from the second on.
I have correctly chaned the URL to that refered to by the 301, like
a good little automaton, but that table.rename ought to be dealt with
as well.
8:24:52 PM 
Categories: Radio
|
