Guard against bad zio-http Request objects, sometimes provoked by malicious requests #3494
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Certain (malicious) requests currently zio-http
Request
objects with aurl
field that encodes to an empty String, provoking an exceptions within tapir zio-http likeAs far as I can tell, these exceptions are harmless and tapir appropriately returns a
500
error response.Nevertheless, maybe it's better not to let bad requests provoke unanticipated exceptions within tapir internals, to guard against those requests instead. That is the intent of this pull request.
Some requests that apparently provoke this (just correlating log times) include