问各位牛人关于url格式的问题，请进哦

urlencode

是个根据汉字转换成的字符串，用来提交请求的。典型的就是看搜索时的url连接。 【 在 bjtulq (与我同行lq) 的大作中提到: 】 : url中通常有这么一句“&Submit=%CC%E1%BD%BB”，我想问一下%CC%E1%BD%BB是什么东西。

貌似是一种编码格式，具体忘了

就是字符集编码前面加上% 转换成二进制直接用utf8什么的解就可以了，编码不定 【 在 luzi 的大作中提到: 】 : 貌似是一种编码格式，具体忘了 : --

【 在 bjtulq 的大作中提到: 】 : url中通常有这么一句“&Submit=%CC%E1%BD%BB”，我想问一下%CC%E1%BD%BB是什么东西。 : -- 查询字符串的特殊编码或者加密。

【 在 bjtulq 的大作中提到: 】 : url中通常有这么一句“&Submit=%CC%E1%BD%BB”，我想问一下%CC%E1%BD%BB是什么东西。 : -- 摘一段： http://www.ietf.org/rfc/rfc1738.txt 2.2. URL Character Encoding Issues URLs are sequences of characters, i.e., letters, digits, and special characters. A URLs may be represented in a variety of ways: e.g., ink on paper, or a sequence of octets in a coded character set. The interpretation of a URL depends only on the identity of the characters used. In most URL schemes, the sequences of characters in different parts of a URL are used to represent sequences of octets used in Internet protocols. For example, in the ftp scheme, the host name, directory name and file names are such sequences of octets, represented by parts of the URL. Within those parts, an octet may be represented by Berners-Lee, Masinter & McCahill [Page 2] RFC 1738 Uniform Resource Locators (URL) December 1994 the chararacter which has that octet as its code within the US-ASCII [20] coded character set. In addition, octets may be encoded by a character triplet consisting of the character "%" followed by the two hexadecimal digits (from "0123456789ABCDEF") which forming the hexadecimal value of the octet. (The characters "abcdef" may also be used in hexadecimal encodings.) Octets must be encoded if they have no corresponding graphic character within the US-ASCII coded character set, if the use of the corresponding character is unsafe, or if the corresponding character is reserved for some other interpretation within the particular URL scheme. No corresponding graphic US-ASCII: URLs are written only with the graphic printable characters of the US-ASCII coded character set. The octets 80-FF hexadecimal are not used in US-ASCII, and the octets 00-1F and 7F hexadecimal represent control characters; these must be encoded. Unsafe: Characters can be unsafe for a number of reasons. The space character is unsafe because significant spaces may disappear and insignificant spaces may be introduced when URLs are transcribed or typeset or subjected to the treatment of word-processing programs. The characters "<" and ">" are unsafe because they are used as the delimiters around URLs in free text; the quote mark (""") is used to delimit URLs in some systems. The character "#" is unsafe and should always be encoded because it is used in World Wide Web and in other systems to delimit a URL from a fragment/anchor identifier that might follow it. The character "%" is unsafe because it is used for encodings of other characters. Other characters are unsafe because gateways and other transport agents are known to sometimes modify such characters. These characters are "{", "}", "|", "\", "^", "~", "[", "]", and "`". All unsafe characters must always be encoded within a URL. For example, the character "#" must be encoded within URLs even in systems that do not normally deal with fragment or anchor identifiers, so that if the URL is copied into another system that does use them, it will not be necessary to change the URL encoding. Berners-Lee, Masinter & McCahill [Page 3] RFC 1738 Uniform Resource Locators (URL) December 1994 Reserved: Many URL schemes reserve certain characters for a special meaning: their appearance in the scheme-specific part of the URL has a designated semantics. If the character corresponding to an octet is reserved in a scheme, the octet must be encoded. The characters ";", "/", "?", ":", "@", "=" and "&" are the characters which may be reserved for special meaning within a scheme. No other characters may be reserved within a scheme. Usually a URL has the same interpretation when an octet is represented by a character and when it encoded. However, this is not true for reserved characters: encoding a character reserved for a particular scheme may change the semantics of a URL. Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL. On the other hand, characters that are not required to be encoded (including alphanumerics) may be encoded within the scheme-specific part of a URL, as long as they are not being used for a reserved purpose.

http://tool.chinaz.com/Tools/URLEncode.aspx,这个是可以查询urlencode编码和解码的网站，查了一下，结果是“提交“，也就是说submit按钮的value=提交

那是中文，utf-8编码

其实这个不定，取决于页面编码 比如baidu 【 在 a6560072 的大作中提到: 】 : 那是中文，utf-8编码 : --