a5dd0f8aa9
According to CGI/1.1 RFC 3875: The server MUST set this variable; if the Script-URI does not include a query component, the QUERY_STRING MUST be defined as an empty string (""). Python's PEP 333(3) allows omitting it in WSGI interface; PHP docs force no requirements; PSGI and Rack specifications require it even if empty. When nginx proxies requests over FastCGI, it always provides QUERY_STRING. and some PHP apps have been observed to fail if it is missing (see issue #201 on GitHub). A drawback of this change (besides a small overhead) is that there will be no easy way to tell a missing query string from an empty one (i.e. requests with or without the "?" character); yet, it's negligible compared to the possible benefits of wider application compatibility. This closes #226 issue on GitHub. |
||
---|---|---|
.. | ||
go | ||
java | ||
node | ||
perl | ||
php | ||
python | ||
ruby | ||
run.py | ||
test_access_log.py | ||
test_configuration.py | ||
test_go_application.py | ||
test_http_header.py | ||
test_java_application.py | ||
test_node_application.py | ||
test_perl_application.py | ||
test_php_application.py | ||
test_php_basic.py | ||
test_python_application.py | ||
test_python_basic.py | ||
test_python_environment.py | ||
test_python_procman.py | ||
test_routing.py | ||
test_ruby_application.py | ||
test_settings.py | ||
test_tls.py | ||
unit.py |