Marshall IHttpRequestFeature.RawTarget #1463
Merged
+583
−10
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.
Description of changes:
The
HttpRequest.Path
andHttpRequest.PathBase
properties contain unescaped representations of the request path; however, it is sometimes useful to have access to the raw (escaped) request path as supplied exactly by the caller. Due to inconsistencies in URL escaping rules (that is, which characters are considered necessary to escape) and to the fact that thePathString
type contains a partial unescaping, it is not possible to reconstruct the original, raw request path from thePath
andPathBase
properties.The
RawTarget
property exists on theIHttpRequestFeature
interface to address the above issue; however, that property is currently not set during request marshalling. This PR updates theMarshallRequest
implementations to set theIHttpRequestFeature.RawTarget
property.All existing unit tests pass and new unit tests have been added to verify new functionality.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.