This patch is a followup to 0dde5052b which added testserver.py, a HTTP echo server for the HttpTests and HttpsTests in the ServicesKit test suite. This patch implements `testserver.py --use-tls` which allows for re-enabling HttpsTests. If `--use-tls` is used, then a self-signed TLS certificate is generated in a temporary directory which is used by the test server. This option is used when running HttpsTests. There doesn't seem to be a good way to have these tests trust the certificate generated by this test at the moment. Until that API exists I've just made these tests ignore certificate validation. We'll want to resolve this and update these tests to actually verify that validation works as expected. Some minor tweaks had to be made to testserver.py to take care of differences in the response body when serving HTTP and HTTPS requests. Some additional changes: * Don't depend on any files outside of src/tests/kits/net/service for these tests. UploadTest was uploading a file from /boot, but I copied it into the test source directory to avoid having these tests break if someone makes an unrelated change. It doesn't really matter what the contents of this file is as long as it doesn't change. * Use BThreadedTestCase. This speeds up the tests considerably, mostly because it means that the different test cases can share the same HttpTest instance, which means there is only a single TestServer instance, and it takes around half a second to bootstrap the test server on my system, and even longer if --use-tls is used. Change-Id: I6d93d390ebd56115365a85109140d175085e1f01 Reviewed-on: https://review.haiku-os.org/c/haiku/+/2260 Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.