.
- Original Message -
From: "DZ-Jay" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, February 13, 2006 7:09 AM
Subject: Re: [twsocket] Encode URL
On Feb 12, 2006, at 22:15, David A. G. wrote:
> The URL must be encoded because may have ill
On Feb 12, 2006, at 22:15, David A. G. wrote:
> The URL must be encoded because may have illegal characters:
>
> The user may enter an URL like:
> http://www.site.com/fol 1/fol 2/file 1.jpg?par=sdf|dfgó.jpg
>
> This URL must be encoded as:
> http://www.site.com/fol%201/fol%202/file%201.jpg?par=sd
> >I don't understand why you need such complex code for doing such simple
> >task as building an url !
> Yes I know, but I'm meaning if we need to process an unknown URL entered by
> user. May be we need a general URL encoder, capable to parse and encode each
> part if necessary in a correct w
, 2006 5:15 AM
Subject: Re: [twsocket] Encode URL
The URL must be encoded because may have illegal characters:
The user may enter an URL like:
http://www.site.com/fol 1/fol 2/file 1.jpg?par=sdf|dfgó.jpg
This URL must be encoded as:
http://www.site.com/fol%201/fol%202/file%201.jpg?par=sdf%
support mailing"
Sent: Sunday, February 12, 2006 11:42 PM
Subject: Re: [twsocket] Encode URL
> David A. G. wrote:
>> Thanks DZ-Jay. I think we need to add a more complete function, ..just
>> what
>> to do if we need to encode (correctly) a full URL to use with HttpC
David A. G. wrote:
> Thanks DZ-Jay. I think we need to add a more complete function, ..just what
> to do if we need to encode (correctly) a full URL to use with HttpCli? ...It
> was my problem the last week!!
>
That would make no sense. The encoder couldn't tell the difference
between real el
>
To: "ICS support mailing"
Sent: Sunday, February 12, 2006 2:20 PM
Subject: Re: [twsocket] Encode URL
>I don't understand why you need such complex code for doing such simple
>task
> as building an url !
> It's just a matter of a few string concatenation and
://www.overbyte.be
- Original Message -
From: "David A. G." <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 12, 2006 5:42 PM
Subject: Re: [twsocket] Encode URL
> Thanks DZ-Jay. I think we need to add a more complete function, ..just
>
ar/uri.pas
enjoy!
David
- Original Message -
From: "DZ-Jay" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 12, 2006 11:13 AM
Subject: Re: [twsocket] Encode URL
> Hello:
> The UrlEncode function is to encode strings to be i
://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "David A. G." <[EMAIL PROTECTED]>
To:
Sent: Sunday, February 12, 2006 2:00 PM
Subject: [twsocket] Encode URL
> Hello all
>
> I'm trying an HTTP-Get softw
Hello:
The UrlEncode function is to encode strings to be included in URLs, by
escaping any invalid characters, not to encode complete URLs. You can
encode a complete URL, for example, when you want to send that URL as a
parameter in the QueryString, but this is not what you want to d
Hello all
I'm trying an HTTP-Get software but I found that UrlEncode (from IcsUrl.pas)
is not working according the protocol.
UrlEncode simply encodes all the URL without taking care of (parse)
Protocol, Folders, File and Data.
Example:
http : // user:[EMAIL PROTECTED] site .com:80/fol 1/fol 2/
Hello all
I'm trying an HTTP-Get software but I found that UrlEncode (from IcsUrl.pas)
is not working according the protocol.
UrlEncode simply encodes all the URL without taking care of (parse)
Protocol, Folders, File and Data.
Example:
http : // user:[EMAIL PROTECTED] site .com:80/fol 1/fol
13 matches
Mail list logo
