While working on the league/uri I stumble upon the following inconsistency regarding URI creation with the following URL: *" http://example.com/p th?q#f "*
*using League\uri implementation: this will throw* *using Diactoros implementation: *"/%20http://example.com/p%20th?q#f%20"; *using Guzzle implementation: *" http://example.com/p%20th?q#f%20"; *using Slim/Nyholm implementation: *"%20http://example.com/p%20th?q#f%20"; According to RFC3986 spaces are forbidden in URI but since all the other implementations except for league\uri depends on parse_url part of the result is possible as parse_url allow spaces in URL. Is this considered a bug or a lack of clarification in PSR-17 ? In all cases would it be possible to consider adding a test suite to covers basic actions regarding PSR7/PSR17 to allow fixing those cases which are not cover by both PSR -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/php-fig/c781d8c9-fb6c-459f-a771-fbe2092c57c3n%40googlegroups.com.
