Hi,
On Sun, Jun 26, 2016, at 06:09, Lebod wrote:
> My complete set up is below. The only difference is the use of
> "example.com"
> instead of the domain for privacy reasons.I was really hoping that a
> gracious person would just point out the mistake in the set up if there
> is
> one...
>
> serv
I could use some help with this one - I took a big leap with enabling
http/2 support and I got knocked back really quick. There seems to be an
issue with POSTs and it seems to be more pronounced with ios devices (as
much as you can trust user agents) but there were some non-ios devices that
seemed
Echo Arief,
Thanks for the reply.
My complete set up is below. The only difference is the use of "example.com"
instead of the domain for privacy reasons.I was really hoping that a
gracious person would just point out the mistake in the set up if there is
one...
server {
listen 80;
listen 443 ss
Hi,
Fixed.
Consider it done.
Thanks Sergey A. Osokin for the info and Kurt Cancemi for the patch.
Regards,
Rik Ske
> Hello,
>
> I attached a trivial patch that fixes the build. OpenSSL removed unused
> error codes and SSL_R_NO_CIPHERS_PASSED was one of them.
>
> Apply with:
> patch -p1 < 0001
