Skip to content
This repository has been archived by the owner on Jan 31, 2020. It is now read-only.

Parsed and unparsed uri is not a same #5

Open
RubtsovAV opened this issue Apr 9, 2016 · 2 comments
Open

Parsed and unparsed uri is not a same #5

RubtsovAV opened this issue Apr 9, 2016 · 2 comments

Comments

@RubtsovAV
Copy link

Example:
$source_uri = '/?#';
$parsed_uri = Zend\Uri\UriFactory::factory($source_uri, 'http');
$unparsed_uri = $parsed_uri->toString();
echo $unparsed_uri; // we see '/', but must be same as source uri

It's because in Zend\Uri::toString() only host check on null. Can you fix it, please, and add check on null with other uri components? It will be more right behavior of this method.

@RubtsovAV RubtsovAV changed the title Parsed and uparsed uri is not a same Parsed and unparsed uri is not a same Apr 9, 2016
@brian978
Copy link

The query string and anchor are empty so there is no reason to put the '?' and '#' characters in the $unparsed_uri

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-uri; a new issue has been opened at laminas/laminas-uri#6.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants