On Thu, Oct 20, 2016 at 09:19:29AM +, Jens Dueholm Christensen wrote:
> On Tuesday, October 18, 2016 08:28 AM Francis Daly wrote,
Hi there,
> > what output do you get when you use the test config in the earlier mail?
>
> Alas I did not try that config yet, but I would assum
o upstream. That
would be at the cost of (e.g.) not being able to serve sdch- or br-encoded
content to the Chrome that asked for it.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
github.io it would
work better? (At least, until that remote web site chooses to redirect
you somewhere else as well.)
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
was used.
Then send a request to vhost1, to vhost2, to vhost1, and to vhost1
again. Did the first two to vhost1 go to the same upstream? And did the
last to vhost1 go to the other upstream?
I'll be interested in seeing your conclusions.
Good luck with it,
o
that request?
> location ~ ^/en/holidays/shared/images {
> root /mnt/nfs/uat/;
> }
>
> When i replace root with alias it has also no effect :-(
"alias" in a regex location has special requirements.
http://nginx.org/r/alias
Cheers,
ould see an indication of what file
nginx tried to serve, if it failed.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
gnored completely in the config.
I'd suggest to check the logs then, to see what is happening instead.
And ensure that you are getting nginx to use the new config, each time
you change it. The logs should show that that has happened too.
Good luck with it,
f
--
Fr
file gets large in
> size quickly.
I'd probably either try to fix the problem that leads to the errors;
or post-process the file to eliminate the duplicates and only store the
processed version.
But neither of those is a direct answer to your question.
Cheers,
f
--
Francis Dal
ple, "/foo/app" and "/appbaz" will both match this
location.
(Effectively, the above is "does the request include the four-character
string /app anywhere?", which is not what the comment suggests that
you wanted.)
f
--
Francis Dalyfran...@daoine.
that if you do not measure a difference,
there is not an important difference to you.
And yes, use "geo" rather than "map" or any other list.
(Or: build one of each in your lab and measure.)
Cheers,
f
--
Francis Dalyfran...@daoine.org
__
suspect that you do not want "proxy_redirect off", though.
http://nginx.org/r/proxy_redirect
If you can show the request-and-response that works for you, then it
might become clear why the request-and-response that fails for you, fails.
Cheers,
f
--
Francis Dalyfran...@daoine.org
g else as well as nginx, or something else
instead of nginx.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
uest: www.example.com/demo?path=xyz
> Docroot: /var/www/example/xyz/
And what would you like nginx to do with *that* request, that is different
from the previous one?
Perhaps the thing that you want achieved, can be achieved somehow.
f
--
Fran
t;.
Something like
map $arg_path $root_bit {
default $arg_path;
"" default;
}
and then later
root /var/www/example/$root_bit;
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Fri, Nov 11, 2016 at 08:30:06AM +, Francis Daly wrote:
> On Thu, Nov 10, 2016 at 06:46:10PM -0500, ulik wrote:
Hi there,
> > # root when path query arg is present
> > if ($arg_path) {
> > root /var/www/example/$arg_path;
> > }
> You c
, then proxy_bind (http://nginx.org/r/proxy_bind) can do what
you want.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
uot; matches from the / after the domain name, to just before the
first # or ?
For this request, that is from /documents to /params
So of these, the second is the location that nginx should use.
f
--
Francis Dalyfran...@daoine.org
__
epth/ifisevil/
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
x API that it uses
had not changed in that time?
I suspect that when someone that does want it takes a look, they will
create a version for nginx-1.11.6 which avoids touching ->default_port
and it will probably work again.
Cheers,
f
--
Francis D
l is to have no-cache on all php files in this subfolder. Any one who
> could help me?
Populate "location ~ ^/admin/*.php$ {}", perhaps?
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ing the browser
or just by deleting the cookie). If the browser presents a cookie,
the server will not send a new one.
And it is only the new one that will be marked "Secure" or not.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
__
has asked for it.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
iguration is something different, then it may be
worth checking module and server versions for compatibility, or confirming
that the config you think is running is the config that is running.
Who knows; maybe there is a problem that can be fixed in the module.
f
--
Franci
t;proxy_redirect" too); or create an "upstream"
called service1.mydomain.org and "proxy_pass" to that.
Note that if your "location" ends in /, you probably want your
"proxy_pass" to end in / too.
Cheers,
f
--
Francis Dalyfran...@dao
y_pass configuration.
> Is there some way I can set the headers at the time of request processing
> itself not just before proxying to upstream servers?
I do not know what you mean by that question.
What headers are you referring to, specifically?
Thanks,
f
--
Francis Dalyfran..
t; directive were active. No "*_pass" directive is active, so
those three directives are effectively unused for this request.
What do you expect your module to report for a request handled in this
location?
That may make it clearer what you are trying to achieve.
(If it does not, f
0.0.1:/abc/def.xml
Did not match: /abc/def.xml
$ curl http://127.0.0.1:8888/abc.txt
Did not match: /abc.txt
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
you have other configuration that you are not showing.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
y using -- or checking the debug
log for the "name was resolved to" or "connect to" lines. Or check the
error log for the "connect" line if the connect failed.
All of those are indirect. tcpdump is probably easiest; but you could
use a "debug_connection 127.0.0.10
on is that if your tomcat instead returns
HTTP 200 with a header X-Accel-Redirect of @fileserver, then in
your (new) "location @fileserver", a proxy_pass would be a POST to
http://file_server/api/v1/files/two.
Does that help in the design of your solutio
mit_rate" directive, then the documentation at
http://nginx.org/r/limit_rate suggests that yes, you can.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
anent;
Untested, but it looks right :-)
You may want to restrict these to the locations that match their prefixes,
depending on what else is happening.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
hings to start working for you.
If you want a separate location{} for your /content urls, you should
still keep "root html" active in it -- http://nginx.org/r/root for
the documentation.
f
--
Francis Dalyfran...@daoine.org
ation above the "regex everything"
one, so that most things that start with /bin/ will use this instead of
the other.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
hould add one?
Depending on what else is in your config, it may be useful to put the
second rewrite within a "location ^~ /wiki/ {}" block.
But if you don't measure a difference when putting it there, in a
"location ~ \.php5 {}" block, or at server{] level, then it does not
m
te that I want to proxy ?
Probably not; you don't, because nginx is not a proxy server.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thu, Dec 15, 2016 at 01:18:55PM +, Francis Daly wrote:
> On Thu, Dec 15, 2016 at 02:30:17PM +0300, Руслан Закиров wrote:
Hi there,
You got the right answer from Maxim.
I had missed that
> > location ~ ^/([A-Z_].*)$ {
> > rewrite ^/(.*
bly does not exist.
The tools that are needed to create it, probably do exist.
All that seems to be missing is the incentive for someone to actually
do the work to build a thing that you would like to exist.
f
--
Francis Dalyfran...@daoine.org
sr/local/nginx/conf/conf/htpasswd" failed (2:
No such file or directory)" in my error log, until I changed the
auth_basic_user_file directive. But perhaps you have the matching
directory structure already.)
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
quot; matches "any byte" in your regex
engine; or whether you can make it match "any byte" (specifically
including the byte that normally represents newline); before you trust
that fully, of course.)
If you don't like map with regex, you can use "geo"
old a binary
> > representation of the first two octets of the connecting ip address.
> That sounds like a good solution. Will using map along with a regex
> slow the server down much?
The usual rule is that if you do not measure the slow-down on your test
system, then there is not a significan
the content at
http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_bind
with the output of your "nginx -v"
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
10.2
Your version does not support using "transparent", or using
"$remote_addr", but it does support proxy_bind.
If you want to use the config you showed, you will need an updated nginx
version.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
to is chosen; it just connects to what it is told to by
the response of the auth_http request that it makes.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
m http://nginx.org/r/upstream
(Although really, I probably wouldn't do it purely in nginx.conf.)
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
nginx might be asking upstream for something like
/EasyPAY/view/LoginMain.aspxEasyPAY/view/System.js?11, which probably
causes it to send 404 to nginx.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ation is supposed to look like.)
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, Jan 31, 2017 at 08:43:23AM +0200, Nikolaos Milas wrote:
> On 19/1/2016 10:58 μμ, Francis Daly wrote:
Hi there,
> I have tried various things with the aliased directories, but I am
> still having the problem.
> My logic is to use a scheme like (see full details in the att
On Wed, Feb 01, 2017 at 06:53:23PM +0200, Nikolaos Milas wrote:
> On 31/1/2017 10:13 μμ, Francis Daly wrote:
Hi there,
Good that you got it working for you.
> By the way, is there some method to define a block of code which can
> be included at various places?
In stock nginx.conf? No
ng else.
Exactly, it is what the source code says:
v->data = r->connection->addr_text.data;
and then you can track where that addr_text.data value is set.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
n
e benefits, according to this
specific analysis.
Maybe it can be explained why the analysis is wrong; maybe some other
analysis can be suggested that will show that there are benefits. But
the justification for the change will probably have to com
e, any module *could* change what that appears to be. So
don't run modules you don't trust, if you want to be able to believe
what your nginx reports its internal state to be.)
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
rver_name, so what you see is what you
asked for.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
erver_protocol
or if you want the whole request:
http://nginx.org/r/$request
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
what do you want nginx to
do when you request the url /vakanz/ -- it may make it clearer what the
config you want to have in nginx.conf is.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
nx.
Make sure that you use an operating system which has decent file caching,
and make sure that you have enough memory that the operating system can
cache these files.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
n
to do busy-work to keep these files "hot",
do just that.
while :; do
find /var/www/html/images -type f -exec cat \{} > /dev/null +
sleep 10
done
I don't recommend it; but it's not my server.
Good luck with it,
f
--
actual cache key that
is used internally in nginx, so that the purge facility can work with it.
(Or possibly the ngx_cache_purge module could be updated to work
transparently with the current nginx cache key behaviour -- I do not
know whether that is possible.)
Good luck with it,
f
--
Franc
or
location ~* ^/app1/(images|css|js|files)/(.*) {
alias /home/username/app1/public/$1/$2;
}
or
location ~* ^/app1/(.*.(js|css))$ {
alias /home/username/app1/public/$1;
}
In each case, the "location"s (particularly the regex one) could be
nested within the match
You'll want to rethink your design, in order to find something that can
do what you want.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ation.)
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
contents
of the file /usr/local/nginx/html/localhost/abc; but I get the contents
of the file /usr/local/nginx/html/abc instead".
But it will be good to be clear on what you expect to happen.
Thanks,
f
--
Francis Dalyfran...@daoine.org
___
looks to me like you want "match the prefix location, and then do
not check the regex locations".
There's a squiggle for that. http://nginx.org/r/location
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx
to share,
I suspect that it could be a welcome addition to the stock code.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
t be to have nginx "do" cgi itself.
Perhaps it should proxy_pass to a http server; perhaps it should
fastcgi_pass to a fastcgi server that knows how to handle the request.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
cal uri.
> It looks a little bit strange to look for the auth_request's URI through
> static files (/usr/local/html).
It does whatever you configured nginx to do with that uri. (Apart from
the "@named" piece, which I'm not sure about.)
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
clarity, could you show the responses you get for a "curl -v"
request to the first http:// address, and then to the (presumably)
returned 301 Location?
That may make it more obvious what is happening, compared to what should
be happening; and may make the solution clear to somebody.
Cheers,
binary_remote_addr
>
> Not sure how to check in a map if that http header is present.
If the http header is absent, the matching variable is empty. So it will
have the value "".
Use that as the first half of your "map" pair.
ending on your requirements, that may be interesting to you.)
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
nother on port 81,
then you will possibly have to make sure that the internal web areas
are happy with being proxy_pass'ed like that -- they may need extra
configuration to know the public url that refers to them if they create
absolute urls within the html they return, for ex
n an earlier reply.
If it does not, then more investigation is needed.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
.
> I have solved my issue with the following.
This will work, with the above caveats.
If you have time to experiment, you may find that the realip module does
something similar in a less fragile way.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
llisecond resolution instead of
> a value of seconds with millisecond resolution.
My reading of http://nginx.org/r/$upstream_response_time says that what
you report should not be happening.
Do you have a sample config / request / response which shows the problem?
Cheers,
f
--
27;t; so if you need that, then you must build your own work-alike
(like you've done); or write or encourage some to write the code to
improve the realip module for this use case.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing
e fills?
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
One difference there is that your fastcgi_pass in IPv4 connects to an
address:port, while in IPv6 it does not.
I would guess that using [::1]:9056 might have a chance of helping.
But only if you can already fetch a file from nginx on IPv6 when fastcgi
is not involved.
Good luck with it,
==
server {
listen 8880;
return 200 "user agent = $http_user_agent; map = $upstreamname\n";
}
==
$ curl -H User-Agent:xxAndroidxx http://localhost:8880/x
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@ngi
On Thu, Mar 09, 2017 at 06:06:05PM -0500, Vanhels wrote:
Hi there,
> The error happens when Listen and fastcgi_pass have the same port address in
> both domains,
What's the error?
What do you do / what do you see / what do you want to see instead?
f
--
Francis Daly
Nothing in the log" usually means that the request is not getting to
nginx at all.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
n
external file which you "include" in your common nginx.conf, and let
*that* file be generated unique per host.
And another option could be to have a common nginx-conf-precursor
which is distributed to all hosts, and then run a pre-processor of your
choice against it to create the individua
at once.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
does correspond
to a directory, then invoke your extra code -- which might be handled
by a fastcgi script you write, or by something you write in one of the
embedded languages in nginx.
It is possible that someone has already wanted the same thing as you,
and written a module to do it.
I'
n pick up...
Is there some part of the previously-mentioned nchan module design or
source that is unclear or inappropriate here?
I suspect that you may have a better chance of getting a specific answer,
if you ask a specific question.
Good luck with it,
f
--
Francis Daly
.origin-server.com";
> proxy_pass http://corporate_proxy;
> }
does everything that you want normally, then something like
> location /subrequest {
> proxy_buffering off;
> proxy_pass_header on;
> proxy_set_header Host "rest_server";
> proxy_pass htt
,}" and "+", since they mean
the same thing and having both is redundant.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ain requests among the http servers; and you can share
certain other requests among the fastcgi servers; but I believe you
can't have a single incoming request balanced across different protocols
in stock nginx.
f
--
Francis Dalyf
On Mon, Apr 03, 2017 at 10:12:04AM +0200, B.R. via nginx wrote:
> On Sat, Apr 1, 2017 at 1:57 PM, Francis Daly wrote:
>
> > If you want to match "word character or plus", use something like [\w+].
> >
>
> Defining a pattern over a simple assertion is kinda
need to tell nginx which requests to deny and which requests to
allow. But before you can do that, you will have to know how to identify
the requests in one of the sets.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
n
wser shows.
If you want the browser not to make a new request, you need to handle
the request internally, within nginx, possibly by means of a proxy_pass
(if the desired resource is only available in another server{}).
Good luck with it,
f
explicit "listen" has an implicit "listen *:80"
when you run as root.
Does
nginx -T | grep -n 'server\|listen'
show any obvious candidates?
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Can you show some requests that you want the client to make of nginx,
and then show the matching requests that you want nginx to make of
the back-end?
You can use "curl" on the nginx machine to make similar requests of the
back-end yourself, to see that actual response details. That might give
stening-ports to the public,
> then I guess we are done.
Until you exhaust resources on your system, nginx does not care how many
listening ports it opens.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
set a default value for
$per_user_port, and make sure that something sensible happens when that
value is used -- probably a response along the lines of "something isn't
fully set up on the server yet; please wait or let us know", so the user
is not
auth_request user guide did you use
for inspiration? It may be that that document can be improved for the
next person.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
it does not suit you to do it.
It's good that you have solved the problem you had.
Cheers,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
at should be happening, then the path to configuring things to allow
to all to happen will become clearer.
Good luck with it,
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
e auth_request lines. If the effective behaviour changes,
then the lines were doing something that matters.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
difficult to test, if you don't want
to read the available source.
Good luck with it!
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
200 with the content
of /usr/local/nginx/html/x, while "curl -i http://127.0.0.3:8080/x";
returns 401 with
WWW-Authenticate: Basic realm="Site Restricted"
What do you see when you do that exact test?
How does it differ from the problem case you reported?
Cheers,
e?
Will your final use case involve a local file, a resource from the 1.2.3.4
server, or something else?
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
701 - 800 of 1833 matches
Mail list logo
