[Webkit-unassigned] [Bug 109287] [GTK] Crash in webkitURIResponseSetCertificateInfo()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=109287





--- Comment #5 from arno. <arno at renevier.net>  2013-02-08 09:38:08 PST ---
(In reply to comment #0)
> 
> The quick fix would be not to call to webkitURIResponseSetCertificateInfo() if the webresource doesn't have yet a response, but I am not sure whether this is the right thing.


Then, when response arrives later, it would not get a certificate info. What are the implications of that ?

Would that work better by always registering a notify::response callback on the main response, and calling setCertificateToMainResource from there ?


Also, even with that patch, there still is problem:
at *third* load of a page with 304 code, the page does not load (try to go to http://localhost/tmp/crash.php at 3rd load, network panel in error console show that the request has been aborted). That is because webkitWebViewDecidePolicy receives the 304 response with a null mimetype the second time (but not the first time). That is probably another bug though.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.