Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=9415





------- Additional Comments From jblosser-smgl AT firinn.org  2005-08-07 17:07 
-------
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > The main problem is, wget doesnt recognize that as an error (and it 
> > > should
IMO).
> > 
> > They aren't going to be seen as errors because they are HTTP status code 
> > 200,
> > which means the server said "this is the file you wanted, we are done".  
> > HTTP
> > 200 is like a 0 exit code in shell.
> 
> In that case the url should be fixed (actually, in all these cases they 
> should
> be, and it's perfectly automatable to check for these problems and report 
> them
> as bugs automatically). Although nearly every case of this ive seen is 301 
> or
> 302. NOT 200. If they're giving 200 and an html file then thats just stupid.

Some of them are probably transient errors; the 0 file size one I got was the
file that came back from one particular sourceforge mirror which I imagine 
will
get fixed on its own at some point.

The 200 html file was one of the apache mirrors that had been taken over by a
domain squatter and was returning some search page for any request it got. 
Obviously a bug and it was reported as such and you removed that mirror from 
the
list, but in the meantime all casts that hit that mirror were failing when 
they
could've (feasibly) gone on to other mirrors.

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.