鑴辨満椤圭洰鐨勫績寰椼�俻ost get鐨勮姹傛渶澶ф暟鎹檺鍒躲��

1.聽聽聽 Get鏂规硶闀垮害闄愬埗

Http Get鏂规硶鎻愪氦鐨勬暟鎹ぇ灏忛暱搴﹀苟娌℃湁闄愬埗锛孒TTP鍗忚瑙勮寖娌℃湁瀵筓RL闀垮害杩涜闄愬埗銆傝繖涓檺鍒舵槸鐗瑰畾鐨勬祻瑙堝櫒鍙婃湇鍔″櫒瀵瑰畠鐨勯檺鍒躲��

濡傦細IE瀵筓RL闀垮害鐨勯檺鍒舵槸2083瀛楄妭(2K+35)銆�

涓嬮潰灏辨槸瀵瑰悇绉嶆祻瑙堝櫒鍜屾湇鍔″櫒鐨勬渶澶у鐞嗚兘鍔涘仛涓�浜涜鏄�.

Microsoft Internet Explorer (Browser)

IE娴忚鍣ㄥURL鐨勬渶澶ч檺鍒朵负2083涓瓧绗︼紝濡傛灉瓒呰繃杩欎釜鏁板瓧锛屾彁浜ゆ寜閽病鏈変换浣曞弽搴斻��

Firefox (Browser)

瀵逛簬Firefox娴忚鍣║RL鐨勯暱搴﹂檺鍒朵负65,536涓瓧绗︺��

Safari (Browser)

URL鏈�澶ч暱搴﹂檺鍒朵负 80,000涓瓧绗︺��

Opera (Browser)

URL鏈�澶ч暱搴﹂檺鍒朵负190,000涓瓧绗︺��

Google (chrome)

URL鏈�澶ч暱搴﹂檺鍒朵负8182涓瓧绗︺��

Apache (Server)

鑳芥帴鍙楁渶澶rl闀垮害涓�8,192涓瓧绗︺��

Microsoft Internet Information Server(IIS)

鑳芥帴鍙楁渶澶rl鐨勯暱搴︿负16,384涓瓧绗︺��

閫氳繃涓婇潰鐨勬暟鎹彲鐭ワ紝涓轰簡璁╂墍鏈夌殑鐢ㄦ埛閮借兘姝ｅ父娴忚锛� URL鏈�濂戒笉瑕佽秴杩嘔E鐨勬渶澶ч暱搴﹂檺鍒�(2083涓瓧绗︼級锛屽綋鐒讹紝濡傛灉URL涓嶇洿鎺ユ彁渚涚粰鐢ㄦ埛锛岃�屾槸鎻愪緵缁欑▼搴忚皟鐢紝杩欐椂鐨勯暱搴﹀氨鍙彈Web鏈嶅姟鍣ㄥ奖鍝嶄簡銆�

娉細瀵逛簬涓枃鐨勪紶閫掞紝鏈�缁堜細涓簎rlencode鍚庣殑缂栫爜褰㈠紡杩涜浼犻�掞紝濡傛灉娴忚鍣ㄧ殑缂栫爜涓篣TF8鐨勮瘽锛屼竴涓眽瀛楁渶缁堢紪鐮佸悗鐨勫瓧绗﹂暱搴︿负9涓瓧绗︺��

鍥犳濡傛灉浣跨敤鐨� GET 鏂规硶锛屾渶澶ч暱搴︾瓑浜嶶RL鏈�澶ч暱搴﹀噺鍘诲疄闄呰矾寰勪腑鐨勫瓧绗︽暟銆�

2.聽聽聽 POST鏂规硶闀垮害闄愬埗

鐞嗚涓婅锛孭OST鏄病鏈夊ぇ灏忛檺鍒剁殑銆侶TTP鍗忚瑙勮寖涔熸病鏈夎繘琛屽ぇ灏忛檺鍒讹紝璧烽檺鍒朵綔鐢ㄧ殑鏄湇鍔″櫒鐨勫鐞嗙▼搴忕殑澶勭悊鑳藉姏銆�

濡傦細鍦═omcat涓嬪彇娑圥OST澶у皬鐨勯檺鍒讹紙Tomcat榛樿2M锛夛紱

棰濄�備紶浜嗕釜2.2m鐨勫浘鐗囪浆base64瀵煎嚭word甯﹀浘鐗囩敤鐩存帴post璇锋眰鎶ラ敊銆傞暱鐐瑰績銆�

鎵撳紑tomcat鐩綍涓嬬殑conf鐩綍锛屾墦寮�server.xml 鏂囦欢锛屼慨鏀�

debug="0"

acceptCount="100"

connectionTimeout="20000"

disableUploadTimeout="true"

port="8080"

redirectPort="8443"

enableLookups="false"

minSpareThreads="25"

maxSpareThreads="75"

maxThreads="150"

maxPostSize="0"

URIEncoding="GBK"

>聽

澧炲姞绾㈣壊瀛椾綋閮ㄥ垎 maxPostSize="0" (璁句负0鏄彇娑圥OST鐨勫ぇ灏忛檺鍒�)

鍒氱湅鍒扮兢閲屽張鏈夊悓瀛﹀湪璇� HTTP 鍗忚涓嬬殑聽Get 璇锋眰鍙傛暟闀垮害鏄湁澶у皬闄愬埗鐨勶紝鏈�澶т笉鑳借秴杩�

聽XX锛岃�� Post 鏄棤闄愬埗鐨勶紝鐪嬪埌杩欓噷锛屾垜鎯充粬浠畾鏄湅澶氫簡涓�浜涗互璁逛紶璁圭殑鍗氬鎴栬�呬功绫嶏紝

瀵艰嚧涓�绉嶇悊瑙ｄ笂鐨勮鍖猴細

1銆侀鍏堝嵆浣挎湁闀垮害闄愬埗锛屼篃鏄檺鍒剁殑鏄暣涓� URI 闀垮害锛岃�屼笉浠呬粎鏄綘鐨勫弬鏁板�兼暟鎹暱搴︺��

2銆丠TTP 鍗忚浠庢湭瑙勫畾 GET/POST 鐨勮姹傞暱搴﹂檺鍒舵槸澶氬皯銆�

The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).聽

聽Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths.

3銆佹墍璋撶殑璇锋眰闀垮害闄愬埗鏄敱娴忚鍣ㄥ拰 web 鏈嶅姟鍣ㄥ喅瀹氬拰璁剧疆鐨勶紝鍚勭娴忚鍣ㄥ拰 web 鏈嶅姟鍣ㄧ殑璁惧畾

鍧囦笉涓�鏍凤紝杩欎緷璧栦簬鍚勪釜娴忚鍣ㄥ巶瀹剁殑瑙勫畾鎴栬�呭彲浠ユ牴鎹� web 鏈嶅姟鍣ㄧ殑澶勭悊鑳藉姏鏉ヨ瀹氥��

The limit is in MSIE and Safari about 2KB, in Opera about 4KB and in Firefox about 8KB, (255 bytes if we count very old browsers). We may thus assume that 8KB is the maximum possible length and that 2KB is a more affordable length to rely on at the server side and that 255 bytes is the safest length to assume that the entire URL will come in.

If the limit is exceeded in either the browser or the server, most will just truncate the characters outside the limit without any warning. Some servers however may send a HTTP 414 error. If you need to send large data, then better use POST instead of GET. Its limit is much higher, but more dependent on the server used than the client. Usually up to around 2GB is allowed by the average webserver. This is also configureable somewhere in the server settings. The average server will display a server-specific error/exception when the POST limit is exceeded, usually as HTTP 500 error.

HTTP 1.1 defines Status Code 414 Request-URI Too Long for the cases where a server-defined limit is reached. You can see further details on RFC 2616. For the case of client-defined limits, there is no sense on the server returning something, because the server won't receive the request at all.

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.

闄� GET VS POST锛�

1銆佸鏁版祻瑙堝櫒瀵逛簬POST閲囩敤涓ら樁娈靛彂閫佹暟鎹殑锛屽厛鍙戦�佽姹傚ご锛屽啀鍙戦�佽姹備綋锛屽嵆浣垮弬鏁板啀灏戝啀鐭紝涔熶細琚垎鎴愪袱涓楠ゆ潵鍙戦�侊紙鐩稿浜嶨ET锛夛紝涔熷氨鏄涓�姝ュ彂閫乭eader鏁版嵁锛岀浜屾鍐嶅彂閫乥ody閮ㄥ垎銆侶TTP鏄簲鐢ㄥ眰鐨勫崗璁紝鑰屽湪浼犺緭灞傛湁浜涙儏鍐礣CP浼氬嚭鐜颁袱娆¤繛缁撶殑杩囩▼锛孒TTP鍗忚鏈韩涓嶄繚瀛樼姸鎬佷俊鎭紝涓�娆¤姹備竴娆″搷搴斻�傚浜嶵CP鑰岃█锛岄�氫俊娆℃暟瓒婂鍙嶈�岄潬鎬ц秺浣庯紝鑳藉湪涓�娆¤繛缁撲腑浼犺緭瀹岄渶瑕佺殑娑堟伅鏄渶鍙潬鐨勶紝灏介噺浣跨敤GET璇锋眰鏉ュ噺灏戠綉缁滆�楁椂銆傚鏋滈�氫俊鏃堕棿澧炲姞锛岃繖娈垫椂闂村鎴风涓庢湇鍔″櫒绔竴鐩翠繚鎸佽繛鎺ョ姸鎬侊紝鍦ㄦ湇鍔″櫒渚ц礋杞藉彲鑳戒細澧炲姞锛屽彲闈犳�т細涓嬮檷銆�

Tips锛氬叧浜庤繖鐐逛綘鍙互鍙傝�冿細Yahoo缃戠珯鎬ц兘浼樺寲鎸囧崡涔嬫湇鍔″櫒绡�

http://segmentfault.com/a/1190000000353790

http://developer.yahoo.com/performance/rules.html

http://blogread.cn/it/article/6100?f=wbYSLOW娉曞垯涓紝涓轰粈涔坹ahoo鎺ㄨ崘鐢℅ET浠ｆ浛POST锛�

涓婇潰杩欑瘒鏂囩珷浠嬬粛浜喡爓ireshark聽鎶撳寘楠岃瘉 post 涓ゆ鍙戝寘锛実et 涓�娆″彂鍖呯殑鍏ㄨ繃绋嬶紝鎺ㄨ崘闃呰銆�

2銆丟ET璇锋眰鑳藉琚玞ache锛孏ET璇锋眰鑳藉琚繚瀛樺湪娴忚鍣ㄧ殑娴忚鍘嗗彶閲岄潰锛堝瘑鐮佺瓑閲嶈鏁版嵁GET鎻愪氦锛屽埆浜烘煡鐪嬪巻鍙茶褰曪紝灏卞彲浠ョ洿鎺ョ湅鍒拌繖浜涚瀵嗘暟鎹級POST涓嶈繘琛岀紦瀛樸��

3銆丟ET鍙傛暟鏄甫鍦║RL鍚庨潰锛屼紶缁烮E涓璘RL鐨勬渶澶у彲鐢ㄩ暱搴︿负2048瀛楃锛屽叾浠栨祻瑙堝櫒瀵筓RL闀垮害闄愬埗瀹炵幇涓婃湁鎵�涓嶅悓銆侾OST璇锋眰鏃犻暱搴﹂檺鍒讹紙鐩墠鐞嗚涓婃槸杩欐牱鐨勶級銆�

4銆丟ET鎻愪氦鐨勬暟鎹ぇ灏忥紝涓嶅悓娴忚鍣ㄧ殑闄愬埗涓嶅悓锛屼竴鑸湪2k-8K涔嬮棿锛孭OST鎻愪氦鏁版嵁姣旇緝澶э紝澶у皬闈犳湇鍔″櫒鐨勮瀹氬�奸檺鍒讹紝鑰屼笖鏌愪簺鏁版嵁鍙兘鐢� POST 鏂规硶銆屾惡甯︺�嶏紝姣斿 file銆�

5銆佸叏閮ㄧ敤POST涓嶆槸鍗佸垎鍚堢悊锛屾渶濂藉厛鎶婅姹傛寜鍔熻兘鍜屽満鏅垎涓嬬被锛屽鏁版嵁璇锋眰棰戠箒锛屾暟鎹笉鏁忔劅涓旀暟鎹噺鍦ㄦ櫘閫氭祻瑙堝櫒鏈�灏忛檺瀹氱殑2k鑼冨洿鍐咃紝杩欐牱鐨勬儏鍐典娇鐢℅ET銆傚叾浠栧湴鏂逛娇鐢≒OST銆�

6銆丟ET 鐨勬湰璐ㄦ槸銆屽緱銆嶏紝鑰� POST 鐨勬湰璐ㄦ槸銆岀粰銆嶃�傝�屼笖锛孏ET 鏄�屽箓绛夈�嶇殑锛屽湪杩欎竴鐐逛笂锛孏ET 琚涓烘槸銆屽畨鍏ㄧ殑銆嶃�備絾瀹為檯涓� server 绔篃鍙互鐢ㄤ綔璧勬簮鏇存柊锛屼絾鏄繖绉嶇敤娉曡繚鍙嶄簡绾﹀畾锛屽鏄撻�犳垚 CSRF锛堣法绔欒姹備吉閫狅級銆�

tomcat7.0.63涔嬪墠锛�

maxPostSizeThe maximum size in bytes of the POST which will be handled by the container FORM URL parameter parsing. The limit can be disabled by setting this attribute to a value聽less than or equal to 0. If not specified, this attribute is set to 2097152 (2 megabytes).

璁剧疆涓�0鍜岃礋鏁板潎鍙互浠ｈ〃涓嶉檺鍒�

tomcat7.0.63锛堝寘鍚級涔嬪悗锛�

maxPostSizeThe maximum size in bytes of the POST which will be handled by the container FORM URL parameter parsing. The limit can be disabled by setting this attribute to a value聽less than zero. If not specified, this attribute is set to 2097152 (2 megabytes).

涓嶅彲浠ヨ缃负0锛屽彧鑳芥槸璐熸暟浠ｈ〃涓嶉檺鍒�

杩樻湁蹇呴』瑕伮�multipart/form-data鎵嶈兘璧锋晥銆�

鍥涚甯歌鐨� POST 鎻愪氦鏁版嵁鏂瑰紡瀵瑰簲鐨刢ontent-type鍙栧��

application/x-www-form-urlencoded

杩欏簲璇ユ槸鏈�甯歌鐨� POST 鎻愪氦鏁版嵁鐨勬柟寮忎簡銆傛祻瑙堝櫒鐨勫師鐢� form 琛ㄥ崟锛屽鏋滀笉璁剧疆 enctype 灞炴�э紝閭ｄ箞鏈�缁堝氨浼氫互 application/x-www-form-urlencoded 鏂瑰紡鎻愪氦鏁版嵁銆傝姹傜被浼间簬涓嬮潰杩欐牱锛堟棤鍏崇殑璇锋眰澶村湪鏈枃涓兘鐪佺暐鎺変簡锛夛細

POST http://www.example.com HTTP/1.1

Content-Type: application/x-www-form-urlencoded;charset=utf-8

title=test&sub%5B%5D=1&sub%5B%5D=2&sub%5B%5D=3

棣栧厛锛孋ontent-Type 琚寚瀹氫负 application/x-www-form-urlencoded锛涘叾娆★紝鎻愪氦鐨勬暟鎹寜鐓� key1=val1&key2=val2 鐨勬柟寮忚繘琛岀紪鐮侊紝key 鍜� val 閮借繘琛屼簡 URL 杞爜銆傚ぇ閮ㄥ垎鏈嶅姟绔瑷�閮藉杩欑鏂瑰紡鏈夊緢濂界殑鏀寔銆�

寰堝鏃跺�欙紝鎴戜滑鐢� Ajax 鎻愪氦鏁版嵁鏃讹紝涔熸槸浣跨敤杩欑鏂瑰紡銆備緥濡� JQuery 鍜� QWrap 鐨� Ajax锛孋ontent-Type 榛樿鍊奸兘鏄�宎pplication/x-www-form-urlencoded;charset=utf-8銆嶃��

multipart/form-data

杩欏張鏄竴涓父瑙佺殑 POST 鏁版嵁鎻愪氦鐨勬柟寮忋�傛垜浠娇鐢ㄨ〃鍗曚笂浼犳枃浠舵椂锛屽繀椤昏 form 鐨� enctyped 绛変簬杩欎釜鍊笺�傜洿鎺ユ潵鐪嬩竴涓姹傜ず渚嬶細

POST http://www.example.com HTTP/1.1

Content-Type:multipart/form-data; boundary=----WebKitFormBoundaryrGKCBY7qhFd3TrwA

------WebKitFormBoundaryrGKCBY7qhFd3TrwA

Content-Disposition: form-data; name="text"

title

------WebKitFormBoundaryrGKCBY7qhFd3TrwA

Content-Disposition: form-data; name="file"; filename="chrome.png"

Content-Type: image/png

PNG ... content of chrome.png ...

------WebKitFormBoundaryrGKCBY7qhFd3TrwA--

杩欎釜渚嬪瓙绋嶅井澶嶆潅鐐广�傞鍏堢敓鎴愪簡涓�涓� boundary 鐢ㄤ簬鍒嗗壊涓嶅悓鐨勫瓧娈碉紝涓轰簡閬垮厤涓庢鏂囧唴瀹归噸澶嶏紝boundary 寰堥暱寰堝鏉傘�傜劧鍚� Content-Type 閲屾寚鏄庝簡鏁版嵁鏄互 mutipart/form-data 鏉ョ紪鐮侊紝鏈璇锋眰鐨� boundary 鏄粈涔堝唴瀹广�傛秷鎭富浣撻噷鎸夌収瀛楁涓暟鍙堝垎涓哄涓粨鏋勭被浼肩殑閮ㄥ垎锛屾瘡閮ㄥ垎閮芥槸浠� --boundary 寮�濮嬶紝绱ф帴鐫�鍐呭鎻忚堪淇℃伅锛岀劧鍚庢槸鍥炶溅锛屾渶鍚庢槸瀛楁鍏蜂綋鍐呭锛堟枃鏈垨浜岃繘鍒讹級銆傚鏋滀紶杈撶殑鏄枃浠讹紝杩樿鍖呭惈鏂囦欢鍚嶅拰鏂囦欢绫诲瀷淇℃伅銆傛秷鎭富浣撴渶鍚庝互 --boundary-- 鏍囩ず缁撴潫銆傚叧浜� mutipart/form-data 鐨勮缁嗗畾涔夛紝璇峰墠寰� rfc1867 鏌ョ湅銆�

杩欑鏂瑰紡涓�鑸敤鏉ヤ笂浼犳枃浠讹紝鍚勫ぇ鏈嶅姟绔瑷�瀵瑰畠涔熸湁鐫�鑹ソ鐨勬敮鎸併��

涓婇潰鎻愬埌鐨勮繖涓ょ POST 鏁版嵁鐨勬柟寮忥紝閮芥槸娴忚鍣ㄥ師鐢熸敮鎸佺殑锛岃�屼笖鐜伴樁娈靛師鐢� form 琛ㄥ崟涔熷彧鏀寔杩欎袱绉嶆柟寮忋�備絾鏄殢鐫�瓒婃潵瓒婂鐨� Web 绔欑偣锛屽挨鍏舵槸 WebApp锛屽叏閮ㄤ娇鐢� Ajax 杩涜鏁版嵁浜や簰涔嬪悗锛屾垜浠畬鍏ㄥ彲浠ュ畾涔夋柊鐨勬暟鎹彁浜ゆ柟寮忥紝缁欏紑鍙戝甫鏉ユ洿澶氫究鍒┿��

application/json

application/json 杩欎釜 Content-Type 浣滀负鍝嶅簲澶村ぇ瀹惰偗瀹氫笉闄岀敓銆傚疄闄呬笂锛岀幇鍦ㄨ秺鏉ヨ秺澶氱殑浜烘妸瀹冧綔涓鸿姹傚ご锛岀敤鏉ュ憡璇夋湇鍔＄娑堟伅涓讳綋鏄簭鍒楀寲鍚庣殑 JSON 瀛楃涓层�傜敱浜� JSON 瑙勮寖鐨勬祦琛岋紝闄や簡浣庣増鏈� IE 涔嬪鐨勫悇澶ф祻瑙堝櫒閮藉師鐢熸敮鎸� JSON.stringify锛屾湇鍔＄璇█涔熼兘鏈夊鐞� JSON 鐨勫嚱鏁帮紝浣跨敤 JSON 涓嶄細閬囦笂浠�涔堥夯鐑︺��

JSON 鏍煎紡鏀寔姣旈敭鍊煎澶嶆潅寰楀鐨勭粨鏋勫寲鏁版嵁锛岃繖涓�鐐逛篃寰堟湁鐢ㄣ�傝寰楁垜鍑犲勾鍓嶅仛涓�涓」鐩椂锛岄渶瑕佹彁浜ょ殑鏁版嵁灞傛闈炲父娣憋紝鎴戝氨鏄妸鏁版嵁 JSON 搴忓垪鍖栦箣鍚庢潵鎻愪氦鐨勩�備笉杩囧綋鏃舵垜鏄妸 JSON 瀛楃涓蹭綔涓� val锛屼粛鐒舵斁鍦ㄩ敭鍊煎閲岋紝浠� x-www-form-urlencoded 鏂瑰紡鎻愪氦銆�

Google 鐨� AngularJS 涓殑 Ajax 鍔熻兘锛岄粯璁ゅ氨鏄彁浜� JSON 瀛楃涓层�備緥濡備笅闈㈣繖娈典唬鐮侊細

var data = {'title':'test', 'sub' : [1,2,3]};

$http.post(url, data).success(function(result) {

...

});

鏈�缁堝彂閫佺殑璇锋眰鏄細

POST http://www.example.com HTTP/1.1

Content-Type: application/json;charset=utf-8

{"title":"test","sub":[1,2,3]}

杩欑鏂规锛屽彲浠ユ柟渚跨殑鎻愪氦澶嶆潅鐨勭粨鏋勫寲鏁版嵁锛岀壒鍒�傚悎 RESTful 鐨勬帴鍙ｃ�傚悇澶ф姄鍖呭伐鍏峰 Chrome 鑷甫鐨勫紑鍙戣�呭伐鍏枫�丗irebug銆丗iddler锛岄兘浼氫互鏍戝舰缁撴瀯灞曠ず JSON 鏁版嵁锛岄潪甯稿弸濂姐�備絾涔熸湁浜涙湇鍔＄璇█杩樻病鏈夋敮鎸佽繖绉嶆柟寮忥紝渚嬪 php 灏辨棤娉曢�氳繃 $_POST 瀵硅薄浠庝笂闈㈢殑璇锋眰涓幏寰楀唴瀹广�傝繖鏃跺�欙紝闇�瑕佽嚜宸卞姩鎵嬪鐞嗕笅锛氬湪璇锋眰澶翠腑 Content-Type 涓� application/json 鏃讹紝浠� php://input 閲岃幏寰楀師濮嬭緭鍏ユ祦锛屽啀 json_decode 鎴愬璞°�備竴浜� php 妗嗘灦宸茬粡寮�濮嬭繖涔堝仛浜嗐��

褰撶劧 AngularJS 涔熷彲浠ラ厤缃负浣跨敤 x-www-form-urlencoded 鏂瑰紡鎻愪氦鏁版嵁銆傚鏈夐渶瑕侊紝鍙互鍙傝�冭繖绡囨枃绔犮��

text/xml

鎴戠殑鍗氬涔嬪墠鎻愬埌杩� XML-RPC锛圶ML Remote Procedure Call锛夈�傚畠鏄竴绉嶄娇鐢� HTTP 浣滀负浼犺緭鍗忚锛孹ML 浣滀负缂栫爜鏂瑰紡鐨勮繙绋嬭皟鐢ㄨ鑼冦�傚吀鍨嬬殑 XML-RPC 璇锋眰鏄繖鏍风殑锛�

POST http://www.example.com HTTP/1.1

Content-Type: text/xml

examples.getStateName

41

XML-RPC 鍗忚绠�鍗曘�佸姛鑳藉鐢紝鍚勭璇█鐨勫疄鐜伴兘鏈夈�傚畠鐨勪娇鐢ㄤ篃寰堝箍娉涳紝濡� WordPress 鐨� XML-RPC Api锛屾悳绱㈠紩鎿庣殑 ping 鏈嶅姟绛夌瓑銆侸avaScript 涓紝涔熸湁鐜版垚鐨勫簱鏀寔浠ヨ繖绉嶆柟寮忚繘琛屾暟鎹氦浜掞紝鑳藉緢濂界殑鏀寔宸叉湁鐨� XML-RPC 鏈嶅姟銆備笉杩囷紝鎴戜釜浜鸿寰� XML 缁撴瀯杩樻槸杩囦簬鑷冭偪锛屼竴鑸満鏅敤 JSON 浼氭洿鐏垫椿鏂逛究銆�

REF锛�

maximum length of HTTP GET request?

http://stackoverflow.com/questions/2659952/maximum-length-of-http-get-request

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.15Request-URI Too Long

http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2.1General Syntax

http://www.cnblogs.com/xiaotaomaomao/articles/986070.html

http://www.cnblogs.com/TankXiao/archive/2012/02/13/2342672.htmlHTTP鍗忚璇﹁В

post鏂瑰紡鐩告瘮get瀹夊叏,鎼哄甫鏁版嵁鏇村ぇ锛屾垜鍑嗗鎵�鏈夋暟鎹兘鐢╬ost鏂瑰紡鑾峰彇锛岃繖鏍峰ソ鍚楋紵

http://segmentfault.com/q/1010000000213082

http://www.cnblogs.com/hyddd/archive/2009/04/09/1432744.html娴呰皥CSRF鏀诲嚮鏂瑰紡