Hello. :) Please consider the following nginx setup:
server {
# server 1
listen 443 default_server ssl;
server_name "";
...
return 444;
}
server {
# server 2
listen 127.0.0.81:443 default_server ssl;
server_name "";
...
return 444;
}
server {
# server 3
Here is what I want to do, in nginx conf language:
server {
listen 80;
server_name www.example.com;
# root when path query arg is present
if ($arg_path) {
root /var/www/example/$arg_path;
}
# root when path query arg is not present (default)
if (!$arg_pat
On Thu, Nov 10, 2016 at 03:04:43PM -0500, ulik wrote:
Hi there,
> Is it possible to set/modify location based on the query string arg from
> request?
The one-word answer is "no".
So the follow-up question is: what do you want to do?
> Here is the scenario:
>
> Request: www.example.com/demo?pa
Is it possible to set/modify location based on the query string arg from
request?
Here is the scenario:
Request: www.example.com/demo?path=abc
Docroot: /var/www/example/abc/
Request: www.example.com/demo?path=xyz
Docroot: /var/www/example/xyz/
Posted at Nginx Forum:
https://forum.nginx.org/rea
Hi Reinis Rozitis, yes it seems to be a plugin.. I am in contact with the
developer to see how to fix it..
Thans for your interest and reply
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,270759,270857#msg-270857
___
nginx mailing list
nginx
add information.
nginx.conf
#user nobody;
worker_processes 1;
#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;
#pidlogs/nginx.pid;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type ap
thanks Igor very insightful :)
I guess tricky issue is for SEO forum closure having SEO friendly http
status code alternative to 503 ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,270850,270854#msg-270854
___
nginx mailing list
nginx@ngi
I was build nginx for window on linux. (compiler: x86_64-w64-mingw32-gcc)
and build succeeded.
but It does not work on any request.. as if it hang status...
I was checked function ngx_event_process_posted in ngx_event_posted.c on
windows gdb.
and found an empty ngx_queue_t at any requested.
how
The behaviour of a single and multiple upstreams is changed due to
'http_503' option of 'fastcgi_next_upstream' .
When a request comes to nginx, nginx forwards it to an upstream, tries
to get a response, gets 503. http 503 is set to be a failed response
(with proxy_next_upstream directive). So
