[fpc-pascal] Re: URIParser

[Ludo Brands]

> How can code distinguish between
>
> protocol:something at somesite
> 
> and
> password:something at somesite

Protocol is missing from the last one = not an URI. A protocol is asumed.
Browsers assume http:, mailers mailto:, telnet assumes telnet:,  etc

Ludo


-----Message d'origine-----
De : fpc-pascal-bounces at lists.freepascal.org
[mailto:fpc-pascal-bounces at lists.freepascal.org] De la part de
michael.vancanneyt at wisa.be
Envoyé : mercredi 18 mai 2011 15:12
À : FPC-Pascal users discussions
Objet : Re: [fpc-pascal] Re: URIParser




On Wed, 18 May 2011, ik wrote:

> On Wed, May 18, 2011 at 15:50, <michael.vancanneyt at wisa.be> wrote:
>
>>
>>
>> On Wed, 18 May 2011, ik wrote:
>>
>>  I've created a more simple example:
>>>
>>> program uri_test;
>>> uses URIParser;
>>>
>>> var
>>>  URI : TURI;
>>>
>>> begin
>>>
>>
>> You don't specify the protocol.
>>
>> a URI starts always with "protocol://"
>>
>> so http://sip:bob@example.com/
>>
>
> The problem is that the SIP URI ( 
> http://tools.ietf.org/html/rfc3261#section-19.1 and
> http://tools.ietf.org/html/rfc3261#section-19.1.1)
> are more like the mailto: URI then the HTTP URI.
>
> RFC 3986 <http://tools.ietf.org/html/rfc3986> does talk about such 
> structure of URI as well.

Hmmm.

How can code distinguish between

protocol:something at somesite

and
password:something at somesite

?

Michael.
_______________________________________________
fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal