You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
For example, I created a rule that just matches on the word "GET", otherwise, it doesn't do anything.
Expected Behavior:
Look at the entire HTTP request for a match, not just the first word.
Steps To Reproduce:
Create rules.yaml with a rule to respond to a GET request
Run 'simplehttpserver -rules rules.yaml -tcp -tls -https -verbose -listen 127.0.0.1:443'
Anything else:
The text was updated successfully, but these errors were encountered:
uBadRequest
added
the
Type: Bug
Inconsistencies or issues which will cause an issue or problem for users or implementors.
label
May 23, 2022
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.
For example, I created a rule that just matches on the word "GET", otherwise, it doesn't do anything.
Expected Behavior:
Look at the entire HTTP request for a match, not just the first word.
Steps To Reproduce:
Anything else:
The text was updated successfully, but these errors were encountered: