From: Dean M. B. <mik...@gm...> - 2009-12-21 11:03:12
|
On Sat, Dec 19, 2009 at 10:26 AM, Dean Michael Berris <mik...@gm...> wrote: > > Sweet! Thanks for doing this, it's very much appreciated. > > Looking forward to your progress soon! :) > Okay, now I've pushed the HTTP Server and client refactoring to support HTTPS connections. However, the tests are broken because the Python server for some reason throws up on POST via HTTPS. The GET/HEAD requests are just fine with the HTTPS server but the POST requests for some reason through CGI seem to break. I don't know enough Python kung fu to fix this, so I'm putting it out in the wild. Branch 0.5-devel as of now has the Python test server which is broken. One option is to write an HTTPS server that doesn't use the CGI scripts -- maybe via WSGI so that we can also handle POST/PUT/DELETE/etc.; I'll leave that up to those with enough Python kung fu to figure out. ;) The test for https on the localhost interface is in libs/network/test/https_localhost_test.cpp -- this is almost identical to the http_localhost_tests but we can change these up so that we can see tests that pass on the https requests. If anybody is willing to change up the tests to go in-line with a non-throwing-up Python HTTPS server and tests, you're very much welcome. Have a great day everyone, and I'm looking forward to suggestions and ideas. I'll move on to implementing chunked encoding support on the HTTP/1.1 front. :D -- Dean Michael Berris blog.cplusplus-soup.com | twitter.com/mikhailberis linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com |