Geek Answers Handbook

URL encoding yes / or no?

I have a quiet web service that receives some structured data that is placed directly in the database.

Data is sent from the OS using wget. I'm just wondering if I really need to encode the URL data, and if so, why? Please note that this is not a problem, but in this case it may not be feasible.

+5
source share
1 answer

If your data has characters that are not allowed in the URLs, you must encode it.

The following characters are either reserved (for example, &), or simply represent an opportunity to confuse the code. If your data contains these characters, enter urlencode. Remember that if you use any extended ascii characters, Unicode characters or non-printable characters, you must encode your data.

  • Dollar ("$")
  • Ampersand ("&")
  • Plus ("+")
  • Comma (",")
  • Forward slash / virgule ("/")
  • Colon (":")
  • Semi-colon (";")
  • Equals ("=")
  • Question mark ( "?" )
  • Symbol "B" ("@")
  • Space
  • Quotation marks
  • Less than symbol ("<")
  • The More Symbol (">")
  • Pound Symbol ("#")
  • Percentage Symbol ("%")
  • ( "{" )
  • ( "}" )
  • / ( "|" )
  • ( "\" )
  • Caret ( "^" )
  • ( "~" )
  • ( "[" )
  • ( "]" )
  • ( "`" )

: http://www.blooberry.com/indexdot/html/topics/urlencoding.htm

+4

More articles:


All Articles