and-backup-td6534435.html
Cheers,
Nicholas Sherlock
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 5 August 2014 00:37, ukr wrote:
> The same behavior happens on nginx 1.7.3
>
Make sure that your Nginx was built with SNI support, by using the -V
switch:
http://nginx.org/en/docs/http/configuring_https_servers.html#sni
___
nginx mailing list
nginx
rtificate that has been *signed* by the
ssl_client_certificate.
You can use the openssl command line tools to verify that your client's
cert is signed correctly:
openssl verify -verbose -CAfile NewCA_Cert.pem client_to_verify.crt
Cheers,
Nicholas Sherlock
__
ur PNG in an image editor to
regenerate the CRC.
Cheers,
Nicholas Sherlock
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
what file type it is. I don't know if it could do that.
You could try just using:
add_header Content-Type image/jpeg;
And hope that the user's web browser will automatically work out the
correct Content-Type, if the image was actually a PNG or something.
t can add latency if your response is very
large. This is controlled by the proxy_buffering setting, so try setting it
to "no":
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering
Cheers,
Nicholas Sherlock
___
nginx mailing l
