You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...but still start_server "limits" the service to http and drops the https requests. I could follow the provided arguments (--ssl-cert, --ssl-key, etc.) down to /usr/share/perl5/Net/Server.pm's _initialize() but then I lost the hope ;)
I also tried providing the arguments with the "--net-server" prefix like --net-server-ssl-cert with gives the same results (#109).
If I start start_server without a port starman/plackup take over and provide an https service with all inner workings (as running it standalone) but then the process managing functions of start_server don't work anymore, because the "restart" procedure in start_server is to launch a new worker and then kill the old one - but as starman/plackup are already using the port a second starman/plackup instance can't sucessfully be start because the Address already in use.
Any thoughts on this?
Thanks
xiconfjs
The text was updated successfully, but these errors were encountered:
Hi,
I don't exactly know if this fits here or in the Server_starter issue queue 😕
I'm starting my dancer2 application via starman (same with plackup) with the following command line...
...but still start_server "limits" the service to http and drops the https requests. I could follow the provided arguments (--ssl-cert, --ssl-key, etc.) down to /usr/share/perl5/Net/Server.pm's _initialize() but then I lost the hope ;)
I also tried providing the arguments with the "--net-server" prefix like --net-server-ssl-cert with gives the same results (#109).
If I start start_server without a port starman/plackup take over and provide an https service with all inner workings (as running it standalone) but then the process managing functions of start_server don't work anymore, because the "restart" procedure in start_server is to launch a new worker and then kill the old one - but as starman/plackup are already using the port a second starman/plackup instance can't sucessfully be start because the Address already in use.
Any thoughts on this?
Thanks
xiconfjs
The text was updated successfully, but these errors were encountered: