Uri::__toString() can yield malformed URIs

[TimWolla]

Bug Report

Q	A
Version(s)	Current git 3.3.x

Summary

The Uri class is able to parse malformed URIs but this results in Uri::__toString() generating a malformed URI. Attempting to pass that URI back into Uri will yield a InvalidArgumentException.

Current behavior

Certain malformed URIs do not round-trip through \Laminas\Diactoros\Uri.

How to reproduce

<?php

require('vendor/autoload.php');

$value = 'http://invalid:%20https://example.com';
$uri = new \Laminas\Diactoros\Uri($value);
$uri2 = new \Laminas\Diactoros\Uri($uri->__toString()); // Exception is thrown here.

Expected behavior

Either both constructors throw, or neither.

---

Note: This issue also exists in guzzlehttp/psr7 and was reported at guzzle/psr7#583.

[froschdesign]

$value = 'http://invalid:%20https://example.com';

PHP's function parse_url can not handle this wrong URL: https://www.php.net/manual/function.parse-url.php#refsect1-function.parse-url-notes

array(3) {
  'scheme' =>
  string(4) "http"
  'host' =>
  string(16) "invalid:%20https"
  'path' =>
  string(13) "//example.com"
}

laminas-diactoros/src/Uri.php

Lines 80 to 87 in 4c6ae00

	public function __construct(string $uri = '')
	{
	if ('' === $uri) {
	return;
	}
	$this->parseUri($uri);
	}

laminas-diactoros/src/Uri.php

Lines 384 to 392 in 4c6ae00

	private function parseUri(string $uri): void
	{
	$parts = parse_url($uri);
	if (false === $parts) {
	throw new Exception\InvalidArgumentException(
	'The source URI string appears to be malformed'
	);
	}

[boesing]

Thanks, @TimWolla for cross posting.

Lets see how guzzle will handle this, after my latest hassle with php-http/discovery I would prefer to keep this in-sync.
We might also want to cross-post this to https://github.com/php-http/psr7-integration-tests (which is used by diactoros as well).