This would be a very nice addition indeed, thanks!! I guess it needs quite
a lot of testing though, ECC certs are still not really common these days.
BTW and before some of the core devs says it patches should be sent in the
email body, not as an attachment. It is much more convenient for reviewin
Hi Manuel,
The weak etag preservation was added to nginx 1.7.3 so I guess your problem
is that you're still on the 1.6.* branch! Hope that helps :)
Albert
On Mon, Oct 6, 2014 at 4:34 PM, Manuel Vázquez wrote:
> Hi all,
>
> I'm not a nginx developer; just an user.
>
> Recently I deployed OpenER
yup, just tested this today and works like a charm, thanks!
On Mon, Jul 21, 2014 at 6:48 PM, Aaron Peschel
wrote:
> Thank you for your help through this whole process, Maxim!
>
> On Wed, Jun 25, 2014 at 3:40 PM, Maxim Dounin wrote:
> > details: http://hg.nginx.org/nginx/rev/e491b26fa5a1
> >
Another one here using dynamic etags generated by the backend that are lost
during the gzip compression; it would indeed ve very nice to have the weak
etag support. The Last Modified header is not always a viable option.
On Tue, Apr 29, 2014 at 8:53 PM, Adam Arsenault <
adam.arsena...@hootsuite.c
Hi all,
We have a media server and we protect certain files from being accessed by
external ips, we just allow access from our static ip. Everything works ok
and a 403 is thrown to those who try to access the files.
server {
listen ***;
root ***;
{some other settings}
# protec
Hi all!
Right now we have compiled our own nginx instance to change the TLS record
size [1], which is fine, but I am wondering if it would be very complicated
to change this for a config option. I am new to the internals of nginx, and
before trying to make a patch it would be nice to have some opi
