-
Notifications
You must be signed in to change notification settings - Fork 57
Custom responses using tls #52
Copy link
Copy link
Labels
Priority: LowThis issue can probably be picked up by anyone looking to contribute to the project, as an entry fixThis issue can probably be picked up by anyone looking to contribute to the project, as an entry fixStatus: CompletedNothing further to be done with this issue. Awaiting to be closed.Nothing further to be done with this issue. Awaiting to be closed.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Metadata
Metadata
Assignees
Labels
Priority: LowThis issue can probably be picked up by anyone looking to contribute to the project, as an entry fixThis issue can probably be picked up by anyone looking to contribute to the project, as an entry fixStatus: CompletedNothing further to be done with this issue. Awaiting to be closed.Nothing further to be done with this issue. Awaiting to be closed.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Forgive me if I've missed something but I'm trying to set up a web server that will respond to POST requests but I'd like to encrypt the communication. Here's my rule file:
But when run with the following (a few I've tried), I get errors thrown from curl:
Server:
simplehttpserver -tcp -rules rules.yaml -listen localhost:443Request:
$ curl -X hey https://localhost/ curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443Server:
simplehttpserver -rules rules.yaml -tcp -tls -domain localhost -listen localhost:443Request:
$ curl -X hey https://localhost/ curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443Am I missing something? It works fine so long as I'm not trying to encrypt.