[prssr-devel-ml] Re: Crashing update

Feeds that cause "error" are downloaded correctly, but the problem is
in MSXML that can not handle them. I tested those with wget to be sure
that the error is not in my HTTP implementation.

Redirection is handled (and implemented) as it is supposed to - no
error ocured for me. If there is an HTTP error, the error message
'HTTP error <number>' appears.

I'll make a special beta for testing this. Now, I have two critical
bugs opened, thus the beta will be out after fixing these bugs.

--
David

On 11/28/05, Hal Rottenberg <halr9000@xxxxxxxxx> wrote:
> On 11/28/05, David Andrs <pda@xxxxxxxxxxxxx> wrote:
> > Anyway, I revert to my own implemetation of HTTP today. I test it on
> > Hal's OPML and most of feeds are updated - some are not, but they were
>
> David,
>
> I've been towing this OPML around for a while.  It is entirely
> possible that some of the feeds are really invalid.  Are you able to
> see the HTTP responses?  I imagine you'd see a 404 in those cases.  In
> fact you should probably also test 301 (moved perm), 307 (moved temp),
> as well as all of the rest of the 400-codes. Some of these codes could
> be handled specially behind the scenes to give the user more
> information as to the error, or even continue without aborting end up
> successfully updating the feed.  e.g. A 301 should look for the news
> feed at the new location header URI, and it should change the prssr
> database to reflect the new URL.
>
> (one more day till my phone/pda arrives!)
>
> --
> Psi webmaster (http://psi-im.org)
> im:hal@xxxxxxxxxxxxxxx
> http://halr9000.com
> --
> pRSSreader development mailing list
> prssr-devel-ml@xxxxxxxxxxxxx
> http://www.freelists.org/archives/prssr-devel-ml
>
>
>
--
pRSSreader development mailing list
prssr-devel-ml@xxxxxxxxxxxxx
http://www.freelists.org/archives/prssr-devel-ml

Other related posts: