-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix content-type "application/x-www-form-urlencoded" failed #184
Conversation
Thank you for the request. |
@artemklevtsov I have added a test case for I dont know why the handler cant extract the params from POST body in Inside the handler, the body is correct: > request$body
[1] "foo=bar&a=b" but the > request$parameters_body
list() |
See example https://github.com/rexyai/RestRserve/blob/master/inst/tinytest/test-cl-request.R#L91-L103 |
Weird, I still did not get the |
Parsing an url-encoded body defined here: Lines 232 to 246 in 96513b9
So we simply convert named vector to list, encode it and convert to raw-vector. |
I see, that makes sense now. because
|
Codecov Report
@@ Coverage Diff @@
## dev #184 +/- ##
==========================================
+ Coverage 95.01% 95.09% +0.07%
==========================================
Files 27 27
Lines 1305 1305
==========================================
+ Hits 1240 1241 +1
+ Misses 65 64 -1
Continue to review full report at Codecov.
|
HTTP request is initially processed by backend (Rserve) and transformed into R object (which is specific per backend). Than this R object is transformed into standard
|
fixes #183