double quotes aren't required in all cases: RFC2965 section 3.1 says value is either a "token" or a "quoted- string". A token is defined as a sequence of non-special, non-white space characters. RFC2616 2.2 lists what can be interpreted as special characters, and '%' is not listed as special.
Therefore, (okay, I'm coming around to agree with current implementation <grin>) one can urlencode the value string, but NOT surround the string by double quotes. -or- one can surround the string with double quotes and include otherwise "special" characters. So The following should be legal and equivalent: email="[email protected]" email=fred%40example.com ... but while legal, the following should not result in a value with an at-sign... it simply contains a percent sign in it, probably not what the application programmer intended: email="fred%40example.com" ... and the following is not legal [email protected] So, urlencode and do not quote the string & everyone goes home safely.... just like current code works. -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
