Issue 77: allow access to raw POST data with "parse_urlencoded" enabled #134
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Problem: when you set
tnt_pass_http_request
toparse_args parse_urlencoded pass_body
, it's impossible to access raw POST body even if there are binary file, for example.This problem caused because
parse_urlencoded
conflicts withpass_body
.In this patch, I've splitted these options to allow them work together.
Config parameters is backward compatible with upstream.
pass_body
will allow you to access request variablebody
that containts unparsed request body.parse_urlencoded
will allow you to access new request variableargs_urlencoded
that will contain table with parsed POST request (likeargs
for GET)NB! If you using
parse_urlencoded
now, you need to changereq.body
toreq.args_urlencoded
in your Lua code. If you using onlypass_body
, no need to change anything.