Some browsers send crippled content-type headers when it comes to XHR, catch them as well
This commit is contained in:
parent
ac3489049f
commit
0ba0030745
1 changed files with 1 additions and 1 deletions
|
@ -563,7 +563,7 @@ function parse_message_header( src )
|
||||||
-- Populate common environment variables
|
-- Populate common environment variables
|
||||||
msg.env = {
|
msg.env = {
|
||||||
CONTENT_LENGTH = msg.headers['Content-Length'];
|
CONTENT_LENGTH = msg.headers['Content-Length'];
|
||||||
CONTENT_TYPE = msg.headers['Content-Type'];
|
CONTENT_TYPE = msg.headers['Content-Type'] or msg.headers['Content-type'];
|
||||||
REQUEST_METHOD = msg.request_method:upper();
|
REQUEST_METHOD = msg.request_method:upper();
|
||||||
REQUEST_URI = msg.request_uri;
|
REQUEST_URI = msg.request_uri;
|
||||||
SCRIPT_NAME = msg.request_uri:gsub("?.+$","");
|
SCRIPT_NAME = msg.request_uri:gsub("?.+$","");
|
||||||
|
|
Loading…
Reference in a new issue