Re: HTTP_Client, HTTP_Request or Net_Url problem
| From: | Markus Fischer | Date: | Wed, 17 May 2006 07:31:32 +0000 |
| Subject: | Re: HTTP_Client, HTTP_Request or Net_Url problem | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42523@lists.php.net to get a copy of this message | ||
Justin Patrin wrote:
>> Now, this is likely possible that this violates the spec, but in this
>> case other Agents can handle this pretty good, so maybe this can done
>> with the PEAR components too?
>>
>
> As Phillipe said, space is not allowed in URLs. Whatever webserver is
> sending the bad redirect *ought* to be fixed.
>
> That said, this case is one that is easily fixable by the agent as
> space (AFAIK) has no special meanung in URLs. This could easily be
> fixed in Net_URL when a URL is given to it, but IMHO it should be done
> as an option so that incorrect URLs can also be detected and an error
> returned.
I through that too, but in real live all browser are capable of handling
a 'space' in 'Location:' header properly without telling the user of an
invalid url. So, as you said, it boils down to:
* what should Net_URL do with invalid URLs?
* Should it be possible to have a valid Net_URL object with an invalid URL?
- Markus