Skip to content

Failing to properly parse incoming HTTP requests #82

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
uBadRequest opened this issue May 23, 2022 · 0 comments
Open

Failing to properly parse incoming HTTP requests #82

uBadRequest opened this issue May 23, 2022 · 0 comments
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@uBadRequest
Copy link

simplehttpserver version: 0.0.5

Current Behavior:

Using rules to respond to incoming HTTPS requests aren't working as intended. If the first word doesn't match, it skips the entire request. The first word is usually the method.

image

For example, I created a rule that just matches on the word "GET", otherwise, it doesn't do anything.

image

Expected Behavior:

Look at the entire HTTP request for a match, not just the first word.

Steps To Reproduce:

  1. Create rules.yaml with a rule to respond to a GET request
  2. Run 'simplehttpserver -rules rules.yaml -tcp -tls -https -verbose -listen 127.0.0.1:443'

Anything else:

@uBadRequest uBadRequest added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label May 23, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

1 participant