Hi Kelson, On Fri, Apr 07, 2006 at 09:43:07AM -0700, Kelson Vibber wrote:
I'm seeing far fewer problems with this one so far!
I did find a page that made RC4 segfault, though.
I tracked the segfault to an image where the src URL was missing a Content-Type header. (The URL also had a content-length of 0, but that alone doesn't cause Dillo any problems.) It occurred whether I pointed Dillo at a page containing the <img> element, or pointed it straight at the image URL.
RC3 does not segfault on this URL. (It just displays an empty page or image.)
I'm reluctant to post the actual URL because it's a web bug, but here are the headers as reported by the libwww HEAD command:
200 OK Cache-Control: private Date: Fri, 07 Apr 2006 16:17:06 GMT Server: Microsoft-IIS/6.0 Content-Length: 0 MicrosoftOfficeWebServer: 5.0_Pub P3P: CP="PUB OTRo" Set-Cookie: SIClientID=108; path=/ X-AspNet-Version: 1.1.4322 X-Powered-By: ASP.NET
Here's the debug output from Dillo:
HTTP warning: Server didn't send Content-Type in header. Type check: [Srv: (null) Det: text/plain] Segmentation fault
I've been trying to put together a test case, but Apache won't let me send a response without a content-type, even through CGI. If I don't create a Content-Type header, it adds one using the default type and encoding.
Thanks a lot for the report! Bug fixed in CVS, please check it. FWIW, I used boa web server. :-) -- Cheers Jorge.-