On 07/03/14 15:30 , Etienne wrote:

On Fri, 07 Mar 2014 11:43:28 +0100, YiannisOSC wrote:

Hello,
I have a vibe.d app running behind an nginx reverse proxy.
What do you think is better, to secure with SSL the nginx proxy so we
have :
client --> https --> nginx --> http --> vibe.d,
or secure vibe.d ? (then i guess we have to somehow take care that is
https://example.com on the client , with header redirects of the proxy
or something)

Any idea?
Thank you

In fact, if you need to secure one place it's quite important to implement security everywhere to avoid leaks.. especially if vibe.d is located on a different server than nginx and you're moving some personal information through the internet!

The question here is what type of certificate you may be looking for. Your nginx server should have a trusted certificate issued by a verified provider, but for your back-end secured connections you can use your own certificate because nobody will get a warning about that.

Good luck!

For now nginx and vibe.d are running on the same server - computer.
A self signed certificate seems to work fine in that case. It is just a
home made test server for now. Thanks!