|
-
Jan 3rd, 2002, 03:44 PM
#1
Thread Starter
Dazed Member
URLEncoder/URLDecoder
What do you guys think about these two classes? Do you think that all URL strings should be inspected to see if the filenames contain any spaces or embeded characters such as #$%+=$ or should URL's all be encoded regardless just to be on the safe side?
-
Jan 4th, 2002, 06:29 AM
#2
Well ...
URL encoding refers to the encoding of the special characters such as spaces and others, am I right? In that case you wouldn't encode a URL string 'just to be on the safer side'. If a URL contains spaces and special characters, these characters will be encoded. If it doesn't, there is no question of encoding.
Or have I misunderstood your question?
.
-
Jan 4th, 2002, 02:09 PM
#3
Thread Starter
Dazed Member
Posted by HoneyBee
If a URL contains spaces and special characters, these characters will be encoded. If it doesn't, there is no question of encoding.
Right. If the URL dosen't contain these characters then the URL wouldn't have to be encoded. But as a precautionary measure if you encoded all URL's you are working with then the ones with special characters would be encoded and the ones without wouldn't. Id rather run them through an encoding process then having to inspect each one.
But as for your first sentence, if the URL does contain special characters then i think you must phiscally encode the string using the URLEncoder class.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|