1.7
Release 1.7.0 is all about making your server secure. And for that, we introduced the new version of the Http protocol: Http/2.
We introduced the option for you to have a secure server or not - for the secure, we're heading to Http/2 and not only https.
All you have to do is answer the question: 'Do you want a secure app (http/2)?' and then BOOM! You've got yourself a secure server.
The certs (generic ones, borrowed from aliv) will be placed in the server folder and will be used to make the secure part of your app. If you want to change the certs, just go to the folder server/cert and change the files.
Node
There's a known issue between Node's Express and the Http/2 module (here), so, for now, Node's sticking to https.
Go
Go http2 server is working smoothly. In Go, if you're working with https, you're working with Http/2 - so, after we configured the secure server, Http/2 was enabled by default.
Keep in mind that's only available to Go 1.6 and higher.
Other changes
- Creates wiki for deploying in heroku, with both MongoHQ and MongoLab;
- Changes server start command for heroku in procfile.txt;
- Removes unecessary deps and updates module versions;
- Adds more tests;
Resources
Http/2 explained - by Daniel Stenberg
Http/2 in go - by Brad Fitzpatrick