updated: static version and new perftests included
https://www.mare-system.de/blog/page/1405201517/
regards,
mex
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251718,251760#msg-251760
___
nginx mailing list
nginx@nginx.org
http://mail
On Mon, Jul 14, 2014 at 4:47 AM, George wrote:
> Thanks for sharing :)
>
> So SPDY/3.1 SSL works ?
Yep, and so do CHACHA20_POLY130 :D
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Am 14.07.2014 14:54 schrieb "Maxim Dounin" :
>
> By default, nginx just sends what's already available. And for
> SSI, it uses chunked encoding.
I don't understand this. In my understanding SSI (the virtual include
directive) goes downstream (e.g. gets some data from a backend) so that the
backen
Maxim Dounin Wrote:
---
> And we even have a trac ticket for this:
>
> http://trac.nginx.org/nginx/ticket/86
A tested workaround with Lua and a single IF with a return then:
location ~ \.php$ {
try_files $uri $uri/ =404;
Hello!
On Mon, Jul 14, 2014 at 08:30:00AM -0400, mex wrote:
> >
> > Just a quick comment: OpenSSL's libs under ".openssl/" isn't a
> > result of OpenSSL's behaviour, but rather a result of "make
> > install" nginx calls (and the ".openssl" install prefix it
> > instructs OpenSSL to use).
> >
Hello!
On Sun, Jul 13, 2014 at 02:49:18PM +0200, Martin Grotzke wrote:
> Hi all,
>
> inspired by the bigpipe pattern I'm wondering if it's possible to send the
> full html head so that the browser can start downloading CSS and javascript
> files.
>
> An idea would be that the proxied backend us
>
> Just a quick comment: OpenSSL's libs under ".openssl/" isn't a
> result of OpenSSL's behaviour, but rather a result of "make
> install" nginx calls (and the ".openssl" install prefix it
> instructs OpenSSL to use).
>
maybe we can have a --with-libressl=/path/to/libressl
or something more
> I think the cleanest solution would be if the backend could receive 1
> request and just split the content/response into chunks and send
> what's
> immediately available (html head + perhaps page header as well) as
> first
> chunk and send the rest afterwards.
sounds tricky ... i must admit, i a
Thanks for sharing :)
So SPDY/3.1 SSL works ?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251740,251748#msg-251748
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
