Hi Cyril, You can run a ZnSecureServer with a specific certificate. See the class comment. But, this is a bit experimental, you need a very specific certificate and I have only seen it work on Linux.
If you front you Seaside app with Nginx, I assume you are doing HTTPS -> HTTP in Nginx. I would suggest you try doing WWS -> WS as well. This does mean that connections are kept open of course (implicit in WebSockets). I have not yet done this myself, but it should work theoretically. The thing is, you will find 100x more info on (correct) TLS/SSL setup on Nginx, and app proxying is totally accepted today. Please let us know how it goes ;-) Sven > On 2 May 2018, at 16:21, Cyril Ferlicot D. <cyril.ferli...@gmail.com> wrote: > > Hi! > > I am trying to deploy a Seaside application that uses Zinc's websockets. > > I use nginx and I have a TLS certificate for the application so I need > to use secure websockets (wss://) and not simple websockets (ws://). > > I got a problem because the client could not access to the server > because it was failing the handshake. > > I could make it work by using nginx to manage the certificate. But I was > wondering if it would be possible with Zinc to give the access to the > certificate to manage the connection instead of doing it via nginx. Is > it possible to do this? > > Thanks in advance. > > -- > Cyril Ferlicot > https://ferlicot.fr >
