The location specified in a redirect response is always normalized, regardless of how the DisablePathNormalizing field is configured on the original request URI.
This behavior can cause issues if the server expects the redirect path to not be escaped. This problem was found while working with Google Drive URIs, where the redirect location contained an asterisk (*) that was then escaped to %2A, leading to an HTTP 500 response.
The location specified in a redirect response is always normalized, regardless of how the
DisablePathNormalizingfield is configured on the original request URI.This behavior can cause issues if the server expects the redirect path to not be escaped. This problem was found while working with Google Drive URIs, where the redirect location contained an asterisk (
*) that was then escaped to%2A, leading to an HTTP 500 response.