EscapedPath() sometimes re-generates the escaped path, especially if the
original path contains unencoded characters like Ñ or literal spaces. When
it does this reconstruction, it works from the decoded path segments, which
is likely why the original %2F encoding was lost in your example. This
seem
Errata: In the second HTTP example I gave:
HTTP /x%2Fx HTTP/1.1
Host example.com
EscapedPath() will return "/x%2Fx", not "/%2F".
Kind regards,
On Tuesday, 29 April 2025 at 18:58:59 UTC-3 Diego Augusto Molina wrote:
> Hi everyone, thank you in advance for reading.
>
> I was trying to use Escape
