I didn't mention this in my original post, but wouldn't I need to encode
spaces as %20? or is that also un-necessary?

Aaron

-----Original Message-----
From: Hans Boldt [mailto:boldt@ca.ibm.com]
Sent: Tuesday, October 15, 2002 9:09 AM
To: web400@midrange.com
Subject: [WEB400] Re: URL encoding


Bartell, Aaron L. (TC) wrote:
> Sure, right after I get done arguing about URL encoding last week I find
> myself writing a socket program that needs to do it.  Boy, if that don't
> beat all;-)
>
> I am sending a stream of XML through a socket connection and am wondering
if
> I need to encode all of the '<', '>', '/', etc with %3C, %3E, and %2F
> respectively?  And any other characters for that matter. . .
>
> I am assuming I do need to do this so I am wondering if somebody knows of
a
> tool that somebody has already created to do the URL encoding so I can
save
> myself some time.

No, URL encoding is only applicable to URL's in an HTML document.
That is, if you have a need to dynamically generate an anchor tag in
your HTML document where the URL includes a query string, the
special characters in the query string need to be properly encoded.
URL encoding does not apply to any other situation.

Cheers!  Hans



_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/web400
or email: WEB400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.