Description

kurobeats

opened on Sep 15, 2021

Issue body actions

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:

rules:
  - match: hey 
    response: |
              HTTP/1.0 200 OK
              Server: httpd/2.0
              x-frame-options: SAMEORIGIN
              x-xss-protection: 1; mode=block
              Date: Fri, 16 Apr 2021 14:30:32 GMT
              Content-Type: text/html
              Connection: close

              hello

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:443
Request: $ curl -X hey https://localhost/ curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443

Server: simplehttpserver -rules rules.yaml -tcp -tls -domain localhost -listen localhost:443
Request: $ curl -X hey https://localhost/ curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443

Am I missing something? It works fine so long as I'm not trying to encrypt.

Activity

1. cyal1 commented on Sep 15, 2021

   

   cyal1

   on Sep 15, 2021

   More actions

   I also encountered this situation

   server : simplehttpserver --https --listen 0.0.0.0:443 -cert example.com.pem -key example.com.key -rules test.yaml -tcp -tls

   HTTP ERROR 502
2. forgedhallpass

   added

   Type: QuestionA query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.

   on Dec 2, 2021
3. forgedhallpass

   assigned

   ehsandeep

   on Dec 2, 2021
4. ehsandeep

   added

   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 fix

   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.

   and removed

   Type: QuestionA query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.

   on Dec 3, 2021
5. ehsandeep

   removed their assignment

   on Dec 3, 2021
6. Mzack9999

   linked a pull request that will close this issueAdding missing logic to enable TCP TLS server #62on Dec 21, 2021
7. Mzack9999

   self-assigned this

   on Dec 21, 2021
8. Mzack9999

   added

   Status: Review NeededThe issue has a PR attached to it which needs to be reviewedThe issue has a PR attached to it which needs to be reviewed

   on Dec 21, 2021
9. ehsandeep commented on Dec 23, 2021

   

   ehsandeep

   on Dec 23, 2021

   Member

   More actions

   @kurobeats @cyal1 this should be now fixed in the dev version with following PR - #62

   Reacted by Anthony Cozamanis
10. ehsandeep

    added

    Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Nothing further to be done with this issue. Awaiting to be closed.

    and removed

    Status: Review NeededThe issue has a PR attached to it which needs to be reviewedThe issue has a PR attached to it which needs to be reviewed

    on Dec 23, 2021
11. kurobeats commented on Dec 23, 2021

    

    kurobeats

    on Dec 23, 2021

    Author

    More actions

    Thank you!
12. kurobeats

    closed this as completedon Dec 23, 2021
13. kurobeats commented on Dec 23, 2021

    

    kurobeats

    on Dec 23, 2021

    Author

    More actions

    oops haha
14. kurobeats

    reopened this on Dec 23, 2021
15. ehsandeep

    linked a pull request that will close this issue0.0.5 Release #74on Apr 18, 2022
16. ehsandeep

    closed this as completedin #74on Apr 18, 2022
17. cyal1 commented on Oct 3, 2022

    

    cyal1

    on Oct 3, 2022

    More actions

    @kurobeats @cyal1 this should be now fixed in the dev version with following PR - #62

    It is not work use Custom Certificate Key

Issue actions