After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588393 - Crash when sniffing a response with no Content Type header
Crash when sniffing a response with no Content Type header
Status: RESOLVED DUPLICATE of bug 588335
Product: libsoup
Classification: Core
Component: HTTP Transport
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2009-07-12 18:01 UTC by Gustavo Noronha (kov)
Modified: 2009-07-12 20:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proposed work-around (1.27 KB, patch)
2009-07-12 18:02 UTC, Gustavo Noronha (kov) 		none Details | Review
backtrace (2.06 KB, text/plain)
2009-07-12 18:07 UTC, Gustavo Noronha (kov) 		  Details

Description Gustavo Noronha (kov) 2009-07-12 18:01:55 UTC 
Hey, I will create a backtrace. I hit this crash because a response had no Content-Type header, but soup_message_headers_get_content_type() returned text/html, while soup_message_headers_get_one() correctly returned NULL. I didn't figure out why this happens, but I think it would be useful to add a sanity check to avoid making ephy/webkit/libsoup crashier with the new release.
Comment 1 Gustavo Noronha (kov) 2009-07-12 18:02:25 UTC 
Created attachment 138292 [details] [review]
proposed work-around
Comment 2 Gustavo Noronha (kov) 2009-07-12 18:07:31 UTC 
Created attachment 138293 [details]
backtrace
Comment 3 Dan Winship 2009-07-12 20:52:02 UTC 
already fixed shortly before you filed this...

*** This bug has been marked as a duplicate of 588335 ***