HTTP請求中,如果是get請求,那么表單參數以name=value&name1=value1的形式附到url的后面,如果是post請求,那么表單參數是在請求體中,也是以name=value&name1=value1的形式在請求體中。通過chrome的開發者工具可以看到如下(這里是可讀的形式,不是真正的HTTP請求協議的請求格式):
get請求:
- RequestURL:http://127.0.0.1:8080/test/test.do?name=mikan&address=street??
- Request?Method:GET??
- Status?Code:200?OK??
- ???
- Request?Headers??
- Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8??
- Accept-Encoding:gzip,deflate,sdch??
- Accept-Language:zh-CN,zh;q=0.8,en;q=0.6??
- AlexaToolbar-ALX_NS_PH:AlexaToolbar/alxg-3.2??
- Connection:keep-alive??
- Cookie:JSESSIONID=74AC93F9F572980B6FC10474CD8EDD8D??
- Host:127.0.0.1:8080??
- Referer:http://127.0.0.1:8080/test/index.jsp??
- User-Agent:Mozilla/5.0?(Windows?NT?6.1)AppleWebKit/537.36?(KHTML,?like?Gecko)?Chrome/33.0.1750.149?Safari/537.36??
- ???
- Query?String?Parameters??
- name:mikan??
- address:street??
- ???
- Response?Headers??
- Content-Length:2??
- Date:Sun,?11?May?2014?10:42:38?GMT??
- Server:Apache-Coyote/1.1??
Post請求:
- RequestURL:http://127.0.0.1:8080/test/test.do??
- Request?Method:POST??
- Status?Code:200?OK??
- ???
- Request?Headers??
- Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8??
- Accept-Encoding:gzip,deflate,sdch??
- Accept-Language:zh-CN,zh;q=0.8,en;q=0.6??
- AlexaToolbar-ALX_NS_PH:AlexaToolbar/alxg-3.2??
- Cache-Control:max-age=0??
- Connection:keep-alive??
- Content-Length:25??
- Content-Type:application/x-www-form-urlencoded??
- Cookie:JSESSIONID=74AC93F9F572980B6FC10474CD8EDD8D??
- Host:127.0.0.1:8080??
- Origin:http://127.0.0.1:8080??
- Referer:http://127.0.0.1:8080/test/index.jsp??
- User-Agent:Mozilla/5.0?(Windows?NT?6.1)AppleWebKit/537.36?(KHTML,?like?Gecko)?Chrome/33.0.1750.149?Safari/537.36??
- ???
- Form?Data??
- name:mikan??
- address:street??
- ???
- Response?Headers??
- Content-Length:2??
- Date:Sun,?11?May?2014?11:05:33?GMT??
- Server:Apache-Coyote/1.1??
這里要注意post請求的Content-Type為application/x-www-form-urlencoded,參數是在請求體中,即上面請求中的Form Data。
?在servlet中,可以通過request.getParameter(name)的形式來獲取表單參數。
?而如果使用原生AJAX POST請求的話:
- function?getXMLHttpRequest()?{??
- ??????????var?xhr;??
- ??????????if(window.ActiveXObject)?{??
- ???????????????????xhr=?new?ActiveXObject("Microsoft.XMLHTTP");??
- ??????????}else?if?(window.XMLHttpRequest)?{??
- ???????????????????xhr=?new?XMLHttpRequest();??
- ??????????}else?{??
- ???????????????????xhr=?null;??
- ??????????}??
- ??????????return?xhr;??
- }??
- ??
- function?save()?{??
- ??????????var?xhr?=?getXMLHttpRequest();??
- ??????????xhr.open("post","http://127.0.0.1:8080/test/test.do");??
- ??????????var?data?=?"name=mikan&address=street...";??
- ??????????xhr.send(data);??
- ??????????xhr.onreadystatechange=?function()?{??
- ???????????????????if(xhr.readyState?==?4?&&?xhr.status?==?200)?{??
- ????????????????????????????alert("returned:"+?xhr.responseText);??
- ???????????????????}??
- ??????????};??
- }??
?
通過chrome的開發者工具看到請求頭如下:
- RequestURL:http://127.0.0.1:8080/test/test.do??
- Request?Method:POST??
- Status?Code:200?OK??
- ???
- Request?Headers??
- Accept:*/*??
- Accept-Encoding:gzip,deflate,sdch??
- Accept-Language:zh-CN,zh;q=0.8,en;q=0.6??
- AlexaToolbar-ALX_NS_PH:AlexaToolbar/alxg-3.2??
- Connection:keep-alive??
- Content-Length:28??
- Content-Type:text/plain;charset=UTF-8??
- Cookie:JSESSIONID=C40C7823648E952E7C6F7D2E687A0A89??
- Host:127.0.0.1:8080??
- Origin:http://127.0.0.1:8080??
- Referer:http://127.0.0.1:8080/test/index.jsp??
- User-Agent:Mozilla/5.0?(Windows?NT?6.1)AppleWebKit/537.36?(KHTML,?like?Gecko)?Chrome/33.0.1750.149?Safari/537.36??
- ???
- Request?Payload??
- name=mikan&address=street??
- ???
- Response?Headers??
- Content-Length:2??
- Date:Sun,?11?May?2014?11:49:23?GMT??
- Server:Apache-Coyote/1.1??
注意請求的Content-Type為text/plain;charset=UTF-8,而請求表單參數在RequestPayload中。
?那么servlet中通過request.getParameter(name)卻是空。為什么呢?而這樣的參數又該怎么樣獲取呢?
為了搞明白這個問題,查了些資料,也看了Tomcat7.0.53關于請求參數處理的源碼,終于搞明白了是怎么回事。
HTTP POST表單請求提交時,使用的Content-Type是application/x-www-form-urlencoded,而使用原生AJAX的POST請求如果不指定請求頭RequestHeader,默認使用的Content-Type是text/plain;charset=UTF-8。
?由于Tomcat對于Content-Type multipart/form-data(文件上傳)和application/x-www-form-urlencoded(POST請求)做了“特殊處理”。下面來看看相關的處理代碼。
Tomcat的HttpServletRequest類的實現類為org.apache.catalina.connector.Request(實際上是org.apache.coyote.Request),而它對處理請求參數的方法為protected void parseParameters(),這個方法中對Content-Type multipart/form-data(文件上傳)和application/x-www-form-urlencoded(POST請求)的處理代碼如下:
- protectedvoid?parseParameters()?{??
- ?????????????
- ???????????parameters.handleQueryParameters();??
- ?????????????
- ???????????if?("multipart/form-data".equals(contentType))?{???
- ????????????????parseParts();??
- ????????????????success?=?true;??
- ????????????????return;??
- ???????????}??
- ???
- ???????????if(!("application/x-www-form-urlencoded".equals(contentType)))?{??
- ????????????????success?=?true;??
- ????????????????return;??
- ???????????}??
- ?????????????
- ?????????????
- ???????????try?{??
- ????????????????if?(readPostBody(formData,?len)!=?len)?{???
- ????????????????????return;??
- ????????????????}??
- ???????????}?catch?(IOException?e)?{??
- ??????????????????
- ????????????????if(context.getLogger().isDebugEnabled())?{??
- ????????????????????context.getLogger().debug(??
- ????????????????????????????sm.getString("coyoteRequest.parseParameters"),e);??
- ????????????????}??
- ????????????????return;??
- ???????????}??
- ???????????parameters.processParameters(formData,?0,?len);???
- ?????????????
- }??
- ???
- ???protected?int?readPostBody(byte?body[],?int?len)??
- ???????throws?IOException?{??
- ???
- ???????int?offset?=?0;??
- ???????do?{??
- ???????????int?inputLen?=?getStream().read(body,?offset,?len?-?offset);??
- ???????????if?(inputLen?<=?0)?{??
- ????????????????return?offset;??
- ???????????}??
- ???????????offset?+=?inputLen;??
- ???????}?while?((len?-?offset)?>?0);??
- ???????return?len;??
- ????}??
從上面代碼可以看出,Content-Type不是application/x-www-form-urlencoded的POST請求是不會讀取請求體數據和進行相應的參數處理的,即不會解析表單數據來放到request parameter map中。所以通過request.getParameter(name)是獲取不到的。
?那么這樣提交的參數我們該怎么獲取呢?
當然是使用最原始的方式,讀取輸入流來獲取了,如下所示:
- privateString?getRequestPayload(HttpServletRequest?req)?{??
- ??????????StringBuildersb?=?new?StringBuilder();??
- ??????????try(BufferedReaderreader?=?req.getReader();)?{??
- ???????????????????char[]buff?=?new?char[1024];??
- ???????????????????intlen;??
- ???????????????????while((len?=?reader.read(buff))?!=?-1)?{??
- ????????????????????????????sb.append(buff,0,?len);??
- ???????????????????}??
- ??????????}catch?(IOException?e)?{??
- ???????????????????e.printStackTrace();??
- ??????????}??
- ??????????returnsb.toString();??
- }??
當然,設置了application/x-www-form-urlencoded的POST請求也可以通過這種方式來獲取。
?所以,在使用原生AJAX POST請求時,需要明確設置Request Header,即:
- xhr.setRequestHeader("Content-Type","application/x-www-form-urlencoded");??
另外,如果使用jquery,我使用1.11.0這個版本來測試,$.ajax post請求是不需要明確設置這個請求頭的,其他版本的本人沒有親自測試過。相信在1.11.0之后的版本也是不需要設置的。不過之前有的就不一定了。這個沒有測試過。
2015-04-17后記:
最近在看書時才真正搞明白,服務器為什么會對表單提交和文件上傳做特殊處理,因為表單提交數據是名值對的方式,且Content-Type為application/x-www-form-urlencoded,而文件上傳服務器需要特殊處理,普通的post請求(Content-Type不是application/x-www-form-urlencoded)數據格式不固定,不一定是名值對的方式,所以服務器無法知道具體的處理方式,所以只能通過獲取原始數據流的方式來進行解析。
jquery在執行post請求時,會設置Content-Type為application/x-www-form-urlencoded,所以服務器能夠正確解析,而使用原生ajax請求時,如果不顯示的設置Content-Type,那么默認是text/plain,這時服務器就不知道怎么解析數據了,所以才只能通過獲取原始數據流的方式來進行解析請求數據。