Uri cannot be constructed for URI reference of absolute path with colon and numbers about psr7 HOT 5 CLOSED

I think this is because the path you've provided contains invalid characters - you can't use a colon. Replace all the colons with %3A and it should work.

from psr7.

Browsers render %3A as :, which can be confusing, but they actually send %3A to servers.

from psr7.

Hi, thanks for the swift reply!

Well, it is not invalid according to https://datatracker.ietf.org/doc/html/rfc3986#appendix-A which includes colons for path segments in this scenario. I would expect Uri to be standards compliant here.

Additionally it's not that colons generally cause this issue. It's only if paired with a number - I guess it's because parse_url is just not meant for URIs but only full URLs and gets confused by an apparent host / port.

from psr7.

There's not much other option if you want to not pass a valid URI through to the Url class (just the path component of a URI is not a URI). Parse URL is not mis-interpreting it - it just is not meant to be given just a path. ;)

from psr7.

RFC 3986 defines URI and URI reference (but most people probably do not distinguish between them). Since test cases for the Uri class accept input values consisting only of paths it is already implying to support URI references (which is a superset of URI) I'd say. I couldn't find an explicit definition of this in https://www.php-fig.org/psr/psr-7/ though.

So I would still say this is a bug in the Uri class because it uses parse_url behind the scenes (which works okay for most scenarios).

I think we can work around this issue for now, but I wanted to raise this issue for the PSR-7 implementation to be more compliant to the web standard here.

from psr7.