Closed jonathonmcmurray closed 3 years ago
Currently, URL parsing splits hostname from path by searching for /
/
e.g. foo://example.com:8042/over/there?name=ferret
foo://example.com:8042/over/there?name=ferret
/over/there?name=ferret
In rare circumstances, it could be possible that a URL has no "path" but does have a query e.g.
foo://example.com:8042?name=ferret
In current implementation, a / is required before the ? to properly parse the path as /?name=ferret.
?
/?name=ferret
Should handle this automatically & insert leading / to path if necessary
Currently, URL parsing splits hostname from path by searching for
/
e.g.
foo://example.com:8042/over/there?name=ferret
/over/there?name=ferret
In rare circumstances, it could be possible that a URL has no "path" but does have a query e.g.
foo://example.com:8042?name=ferret
In current implementation, a
/
is required before the?
to properly parse the path as/?name=ferret
.Should handle this automatically & insert leading
/
to path if necessary