Skip to content
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

proxy: refactor request/response format #184

Closed
jkasarherou opened this issue Sep 21, 2015 · 3 comments
Closed

proxy: refactor request/response format #184

jkasarherou opened this issue Sep 21, 2015 · 3 comments

Comments

@jkasarherou
Copy link
Contributor

jkasarherou commented Sep 21, 2015

Actually, the proxy uses a mix of headers, query parameters, and field JSON encoded in the request body. We should stop using headers at all (we have full control on the request/response body format) and  use JSON.
Example: To set properties on a container creation:
instead of sending parameters as headers (which is confusing for parameters case sensitivity), we should simply use the JSON encoded body.

@jfsmig
Copy link
Contributor

jfsmig commented Aug 4, 2016

🆙

@jkasarherou
Copy link
Contributor Author

let's do this

@jfsmig
Copy link
Contributor

jfsmig commented Sep 27, 2016

A lot of improvements have been done here, in a round ended with #686 .

@jfsmig jfsmig closed this as completed Sep 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants