http://bugs.winehq.org/show_bug.cgi?id=16831
--- Comment #24 from TJ support@tjworld.net 2009-01-09 08:53:44 --- Created an attachment (id=18595) --> (http://bugs.winehq.org/attachment.cgi?id=18595) Add secure connections tests to test suite
You'll want to replace www.audible.com with test.winehq.org or codeweavers.com (which has https enabled), so we don't burden audible.com.
I've added the tests to the test suite. I *think* I've used the correct mechanisms (based on studying other tests) but I'd welcome review of the attached patch. I basically ported my stand-alone tests. Have I understood the use of "todo_wine" correctly?
Alas, testing against codeweavers HTTPS server actually causes a test to succeed that is expected to fail:
http.c:2209: Test failed: test_secure_url (http:// www.codeweavers.com :443 (null) ) failed, expected error 12152, got error 0
The reason is, the codeweavers HTTPS server has been configured to handle HTTP requests nicely! Is there an alternative host to target which ignores HTTP on HTTPS ?