Bug 19146

Summary: [CURL] https pages not loading.
Product: WebKit Reporter: Kurt H Maier <karmaflux>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, jchaffraix, landry, michael.s.gilbert, sandshrew, tofu.linden
Priority: P2 Keywords: Curl
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Linux   

Kurt H Maier
Reported 2008-05-20 09:43:34 PDT
This is with r33475. https pages (using latest midori revision from git) just don't load. Curl can load them fine on the command line. Please advise me as to what debug output I can post to help clarify this bug. Thanks.
Attachments
Julien Chaffraix
Comment 1 2008-05-29 06:13:16 PDT
> https pages (using latest midori revision from git) just don't load. Curl can > load them fine on the command line. Sounds like a SSL certificate error. A workaround is to set the WEBKIT_IGNORE_SSL_ERRORS environment variable. If it enables SSL pages to work, then it means that you have to update libcURL certificate file (or leave the variable to ignore those errors). > Please advise me as to what debug output I can post to help clarify this bug. The best way to have some debug output is to build a debug build (--enable-debug in configure or --debug in build-webkit) which would display the error you have (bear in mind that it enables additionnal checks and is therefore a bit slower).
Landry Breuil
Comment 2 2008-07-09 13:48:13 PDT
Using curl 7.18.2/webkit 1.0.1/midori 0.18 on OpenBSD/i386, i can reproduce this issue. No certificate nor authority is bundled with our curl package though. Will try with a debug build for more information.
Michael Gilbert
Comment 3 2008-12-30 09:12:27 PST
*** Bug 23031 has been marked as a duplicate of this bug. ***
Brent Fulgham
Comment 4 2009-08-11 22:36:41 PDT
I believe the cause of this bug was resolved by Bug 28171. The point may be moot, now that the Linux port is using SOUP. Please reopen if the problem is still valid for your platform using the current WebKit revision.
Note You need to log in before you can comment on or make changes to this bug.