In reviewing Parameter is not valid errors in Exceptions table, it appears that this may be due to 304 responses.
In testing, I get this error on images returned. Using firebug to see what exactly comes back when these particular absoluteuri images are requested, I see that the first time I get a 200 and on a refresh I get a 304 not returned probably due to caching on the server end.
Debugging ImageManager, I think what is happening is that the image is actually not being returned, so line 96 is trying to do a FromStream call when the stream is a 0 byte stream (nothing returned so nothing there).
So need to look at how 304 respones are handled for images and maybe other things as well.
Kevin
Not all WebServers handle the 'Accept-Type' HttpHeader properly. Fixed in, 1.2 or greater.
An open source .NET web crawler written in C# using SQL 2008.
Join the arachnode.net group on Facebook: http://www.facebook.com/groups.php?ref=sb#/group.php?gid=166721755872
Twitter: http://twitter.com/arachnode_net
arachnode.net is provides custom crawling and contracting resources. Please ask.
http://bit.ly/TOFX4
I wonder if this is due to making a HEAD request first?