-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
[IMPROVEMENT] Compress JSON instead of sending it in a "nice" format #9057
Comments
TODO: |
I would like to be assigned on this one. |
@anuardaher feel free to submit a pull request to add this functionality. 👍 |
I'd like to work on this issue. Could we gZip the incoming JSON response to compress it down? |
No. We will leave the gzipping to the web server, such as caddy or ngnix or Apache. But feel free to submit the pull request for what the issue here describes. 👍🏼 |
Is the ngnix(/caddy/Apache) configuration already done in the repo? I couldn't pinpoint the code suggesting that. |
You are over thinking it 😁 Basically the idea is turn pretty print off and let reverse proxies take care of compression. In the API declaration there is a property to enable pretty print. So just flipping it off if node_env=production is all that's needed :) |
@geekgonecrazy thank you. I wanted to say something but didn't as I'm pretty grumpy today. as that song goes, "you took the words right out of my mouth" |
@geekgonecrazy Yep, I got that but I thought maybe I was oversimplifying it :P |
Nevermind, I figured it out. Here is a PR regarding the same. Just about the time I referenced this PR, I noticed that @graywolf336 worked on the same issue as well :D #9070 |
Description:
Today the REST APIs are returning with spaces and line-breakers. We could remove everything and reduce the payload size with that.
Server Setup Information:
Steps to Reproduce:
Expected behavior:
Example of commands API:
Actual behavior:
The text was updated successfully, but these errors were encountered: