Hello, I am new to nginx and Speedgrade suggest I enable keepalive to
enhance performance of my website(s).
I've read*1 that enabling this is also a risk. What is the best practise?
*1 https://www.nginx.com/blog/http-keepalives-and-web-performance/
Posted at Nginx Forum:
https://forum.nginx.o
I am trying to track down what is going on but an not having any success. I
am using nginx as a proxy for ssl in front of my nodejs app. The http api
works fine. I have the websocket on a separate subdomain. I connects
sometimes but I have a ton of these messages in the error_log:
upstream prematu
Hi folks
We're going to have the first Bay Area OpenResty meetup tomorrow
evening, in CloudFlare's office, as originally planned about one month
ago.
When:
5:30pm ~ 6:30pm, 9 March 2016
Where:
101 Townsend St
San Francisco CA
Fee:
Free.
Meetup website:
http://www.meetup
Thanks a lot for providing a working example. I reproduced it and yes works
with that server block. Then I tried to change until I discovered the
following. Here is my server block:
server {
listen 443 ssl;
listen 8080;
serv
Ok, thanks. I will post this over there.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265157,265161#msg-265161
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Yeah, here's the outputs:
nginx -V
nginx version: nginx/1.9.9
configure arguments: --prefix=/path/to/my/module --with-debug
--with-ld-opt=-lm
config (with some names changed):
events {
worker_connections 1046;
}
http {
my_set_int 1;
my_set_string /path/to/a/data/file;
This may be more appropriate for the nginx-devel list. Additionally, when you
post there you'll probably want to include your modules source so people can
actually assist in debugging.
> On Mar 8, 2016, at 05:01, ben5192 wrote:
>
> Hi,
> I am working on a module for NGINX and am having a prob
Hi.
Am 08-03-2016 14:01, schrieb ben5192:
Hi,
I am working on a module for NGINX and am having a problem with memory
leaking when using "./nginx -s reload". Everything that is allocated is
done
so through ngx_palloc or ngx_pcalloc so NGINX should know to clean it
up. I
have also added a funct
Hi,
I am working on a module for NGINX and am having a problem with memory
leaking when using "./nginx -s reload". Everything that is allocated is done
so through ngx_palloc or ngx_pcalloc so NGINX should know to clean it up. I
have also added a function to exit process which uses ngx_pfree on
ever
Hi,
I'm using nginx as a reverse proxy with caching on a ramdisk
/var/cache/nginx is a tmpfs of the size 1800m.
And this is my proxy_cache_path line in nginx:
proxy_cache_path /var/cache/nginx levels=1:2 use_temp_path=off
keys_zone=default:50m inactive=120m max_size=1500m;
This is the error mess
Hi.
Am 08-03-2016 08:44, schrieb Krishna Kumar K K:
Thing is its failing in the vulnerability scan (nexpose tool is used)
saying cookie is not secure or httponly.
As Aapo said the request header is a client header.
This is only changeable at client side with some javascript code.
If you want
11 matches
Mail list logo
