Bug 17426

Summary:

XMLHttpRequest status remains zero if requesting over HTTPS from a server with a self-signed certificate

Product:

WebKit

Reporter:

Alexey Proskuryakov <ap>

Component:

XML

Assignee:

Alexey Proskuryakov <ap>

Status:

NEW

Severity:

Normal

CC:

emacemac7, jchaffraix

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Mac

OS:

OS X 10.5

Attachments:

Description	Flags
test case	none
test case #2	none

Alexey Proskuryakov

Reported 2008-02-18 11:19:23 PST

I've seen a report of XMLHTTPRequest returning a wrong (zero) status when making an HTTP request to a server with a self-signed certificate. Since bugs.webkit.org currently has a self-signed certificate, this is a handy server to do some testing.

Attachments
test case (443 bytes, text/html) 2008-02-18 11:19 PST, Alexey Proskuryakov	no flags	Details
test case #2 (454 bytes, text/html) 2008-02-18 11:21 PST, Alexey Proskuryakov	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Alexey Proskuryakov

Comment 1 2008-02-18 11:19:52 PST

Created attachment 19191 [details] test case

Alexey Proskuryakov

Comment 2 2008-02-18 11:21:23 PST

Created attachment 19192 [details] test case #2

Alexey Proskuryakov

Comment 3 2008-02-26 09:45:49 PST

This is a bug indeed - but one needs to access the server from a local HTML file (if you have already visited the site, there is no problem, and you cannot currently make cross-site requests unless you are a local file).

Alexey Proskuryakov

Comment 4 2010-05-18 12:22:25 PDT

<rdar://problem/5739559>

Alexey Proskuryakov

Comment 5 2010-05-18 12:36:39 PDT

I'm not sure why I thought that this was a bug. I'm now testing with WebKit test server (https://127.0.0.1:8443), and Firefox doesn't warn about the certificate being self-signed and expired. But Safari warns about it when opening a resource directly, so it seems to make sense that XMLHttpRequest fails.

Note You need to log in before you can comment on or make changes to this bug.