Hi,
I have 3 maps defined
map $request_method $requestnocache {
default 0;
POST1;
}
map $query_string $querystringnc {
default 1;
""0;
}
map $http_cookie $mccookienocache {
default 0;
_mcnc
Hi, glad to see you here.
"The directive configures a timeout to be used when gracefully shutting
down worker processes. When the timer expires, nginx will try to close all
the connections currently open to facilitate shutdown."
Well, if the only purpose is to close all the connections those
Hi,
In my case, I need to add new server block from time to time in nginx. after
reloading, it is observed that the newly added server is not available for
seconds. is this as expected? how to improve it?
BR,
Joe___
nginx mailing list
Hi,
Just have a doubt in map directive
map $http_user_agent $upstreamname {
default desktop;
~(iPhone|Android) mobile;
}
is correct ?
or does the regex need to fully match the variable?
map $http_user_agent $upstreamname {
default desktop;
~*.*Android.* mobile;
Hi,
In my case, I need to add new server block from time to time in nginx. after
reloading, it is observed that the newly added server is not available for
seconds. is this as expected? how to improve it?
BR,
Joe___
nginx mailing list
Hello!
Looks like to me that the original patch does what it's supposed to do
(when combined with http://hg.nginx.org/nginx/rev/3069dd358ba2). Here is my
understanding:
Before this patch, an active connection could potentially delay shutdown
indefinitely due to the presence of connection related
I'm new using nginx, I see the difference in performance, my question is
the following I have the following virtual host: example.conf
[example.conf]
# create new
server {
listen 80;
server_name www.example.com;
location / {
root /home/example/public_html;
On Wed, Mar 08, 2017 at 01:56:04AM -0500, c0nw0nk wrote:
Hi there,
> The usage of the final output is as easy as this. "$client_ip_output;"
> limit_req_zone $client_ip_output zone=one:10m rate=1r/s; #usage example for
> the resulting output after all fallback checks and ip whitelist checks etc.
On Tue, Mar 07, 2017 at 06:44:05PM -0500, c0nw0nk wrote:
Hi there,
> I was just looking at the realip module but that module does not seem to
> support fallback methods like I demonstrated I was in need of.
I'm not convinced that you need anything other than what the realip module
provides; but
Hello everyone,
I am in the process of creating a module that connects to the outside to
exchange data with another service, I am taking as inspiration the
mail_module and the upstream module, basically my module is connecting
using the ngx_event_connect_peer and handling the read and write
is IP_BIND_ADDRESS_NO_PORT the best solution for OP's case? Unlike the
blog post with two backends, OP's case has one backend server. If any
of the hash slots exceed the 65K port limit, there's no chance to
recover. Despite having enough port capacity, the client will receive
an error if the
# HG changeset patch
# User Jürno Ader
# Date 1488987398 -7200
# Wed Mar 08 17:36:38 2017 +0200
# Node ID 9c13ae0d54a75902945bc6ac9bbced1c298fdaa0
# Parent d450723755728f9d0cc291247b9601e2f3340f19
SSL: Added crl_check_mode
Added crl_check_mode flag which can be used to
We are using wowza streaming engine to record Live TV shows which gives
recorded output in the mp4 format. We are evaluating Nginx RTMP module to do
same mp4 recording. However it is observed that this module does recording
only in the flv format. Is there any way to do direct recording of live
Hello BR,Thank you for your answer and for the hints. I'll investigate further
in that direction.Have a nice week
Le Mercredi 8 mars 2017 14h03, B.R. via nginx a écrit :
This clearly looks like an application problem and not a nginx-related one.
nginx does not remove
I'm wondering if RTP hint tracks in MP4 files are necessary to provide
progressive download functionality over my NGINX server configuration. I
can't remember where but I read somewhere that these additional tracks
support the server by seeking operations (byte-range).
Thanks for your feedback,
This clearly looks like an application problem and not a nginx-related one.
nginx does not remove cookies nor, as the configuration snippet you shared
suggest, handles authentication.
If you use DNS, make sure all requests are served by the instance of nginx
you quote, including redirects which
On 3/7/17 10:50 PM, larsg wrote:
> Hi,
>
> we are operating native nginx 1.8.1 on RHEL as a reverse proxy.
> The nginx routes requests to a backend server that can be reached from the
> proxy via a single internal IP address.
> We have to support a large number of concurrent websocket connections
On 3/8/17 3:57 AM, Tolga Ceylan wrote:
> Of course, with split_clients, you are at the mercy of the hashing and
> hope that this distribution will spread work
> evenly based on incoming client address space and the duration of
> these connections, so you might run into
> the limits despite having
I suspect nginx' team chose this value for the very reason it was adapted
to the use of Apache (remember that nginx is, since its beginning, largely
used as a reverse Web proxy in front of Apache farms).
I guess the intent here is to probably mimic Apache behavior by default so
adoption of that
This kind of logic, as you found out, can be handled in nginx with the help
of the proper tools, namely the map module.
You are one step away: you can actually program what you require to be
feeding the realip module with the HTTP header name you ended up with.
Rather than having contiguous maps,
20 matches
Mail list logo