ensure suspected blossom request hash does not have slashes in it #37
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.
I noticed certain URLs would be caught by the blossom url handler if they coincidentally split at 64 bytes. I am using a few extra path handlers.
This change adds a check for slashes. I was thinking a regex test might be better, but perhaps too resource heavy so just kept it as a Index call. Let me know if you prefer a regex test instead.