You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2018. It is now read-only.
I bumped into something unexpected when switching from aleph to clj-http-lite. For some reason nested form params are sent differently despite their respective generate-query-string functions returning identical values.
The REPL session below makes this fairly easy to see by using httpbin.org:
If you manually account for the nesting as below things work as expected:
(deffp {"map[key1]""a""map[key2]""b"})
It's fine to do the above but I'm just confused how :body is set to the same value that aleph would use in wrap-form-params and yet what is sent is somehow different.
The text was updated successfully, but these errors were encountered:
martinklepsch
changed the title
Unexpected form-params treatment
Unexpected nested form-params treatment
Jun 5, 2018
I bumped into something unexpected when switching from aleph to
clj-http-lite
. For some reason nested form params are sent differently despite their respectivegenerate-query-string
functions returning identical values.The REPL session below makes this fairly easy to see by using httpbin.org:
If you manually account for the nesting as below things work as expected:
It's fine to do the above but I'm just confused how
:body
is set to the same value that aleph would use inwrap-form-params
and yet what is sent is somehow different.The text was updated successfully, but these errors were encountered: