Re: [twsocket] Encode URL

2006-02-13 Thread DZ-Jay
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:

Re: [twsocket] Encode URL

2006-02-13 Thread David A. G.
. - Original Message - From: DZ-Jay [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org 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 illegal characters

Re: [twsocket] Encode URL

2006-02-12 Thread DZ-Jay
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

Re: [twsocket] Encode URL

2006-02-12 Thread Francois PIETTE
I already answer that question (or very similar) one or two days ago ! The answer was: UrlEncode is not to encode an URL but to encode a string to be part of an URL, escaping unallowed charcaters in an URL. If you need to parse an URL, use ParseUrl. -- Contribute to the SSL Effort. Visit

Re: [twsocket] Encode URL

2006-02-12 Thread David A. G.
enjoy! David - Original Message - From: DZ-Jay [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Sunday, February 12, 2006 11:13 AM Subject: Re: [twsocket] Encode URL Hello: The UrlEncode function is to encode strings to be included in URLs, by escaping any invalid

Re: [twsocket] Encode URL

2006-02-12 Thread Francois PIETTE
mailing twsocket@elists.org 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 what to do if we need to encode (correctly) a full URL to use with HttpCli? ...It was my problem the last week!! I

Re: [twsocket] Encode URL

2006-02-12 Thread David A. G.
mailing twsocket@elists.org 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 calling UrlEncode for the parameters

Re: [twsocket] Encode URL

2006-02-12 Thread Nicholas Sherlock
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

Re: [twsocket] Encode URL

2006-02-12 Thread David A. G.
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 HttpCli? ...It was my problem the last week!! That would

Re: [twsocket] Encode URL

2006-02-12 Thread Fastream Technologies
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%7Cdfg%F3.jpg This kind