.*
On Sun, Mar 10, 2013 at 6:46 AM, Francis Daly fran...@daoine.org wrote:
On Sun, Mar 10, 2013 at 05:29:18AM -0400, B.R. wrote:
Hi there,
The *correct* way:
location ^~ /documents/(\w+) {
set $user $1;
if ($user != $remote_user) {
return 503;
}
}
Although
Hello,
@Maxim
I tried the duplicate configuration entries:
listen 80;
listen [::]:80 ipv6only=on;
I has the following error:
nginx: [emerg] duplicate listen options for [::]:80 in
/etc/nginx/conf.d/***.conf:3
@Ted
I tested your solution but as I expected nginx is only listening on IPv4
Hmm...
@Maxim
I guess I haven't understood your piece of advice, since 'listen' can only
be used in 'server' directive...
What is it you wanted me to try, again? :oD
---
*B. R.*
On Fri, Apr 5, 2013 at 8:02 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
I have indeed several virtual servers.
I have
trouble comes from bad IPv6 routing, not from
the webserver.
Thanks for your input, everyone!
---
*B. R.*
On Fri, Apr 5, 2013 at 8:48 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
Hmm...
@Maxim
I guess I haven't understood your piece of advice, since 'listen' can only
be used in 'server' directive
[::]:443 ssl ipv6only=on;
server_name one;
...
}
--
Igor Sysoev
http://nginx.com/services.html
On Apr 6, 2013, at 19:01 , B.R. wrote:
Add-on:
Besides, as I explained earlier, having generic 'listen' directives
implies some difficulties.
For example, I am using 2 virtual
After a very long search on Google (almost 15s, including keyboard input),
I found astonishing help, based on the information you provided.
About the FPM children burying, I found a resource on StackOverflow linking
back to the Nginx forum (ML archive):
Why would Nginx automatically redirect mydomain.com do mydomain.com/w/ if
you don't tell it to do so?
Your error log shows that you are trying to list the files of your root
directory (so it means you don't have an index file to be served there),
which is forbidden by default Nginx configuration
I would add to Patrick answer the following:
- 1.1.19 is a development version. IMHO it is always better to prefer
stable in production environments. 1.2.8 or 1.4.1 depending on your
needs/requirements.
- Check the changes from 1.2 or 1.4 http://nginx.org/en/download.html to
decide what is better
Hello,
Is Wheezy supported for Nginx?
Would it be possible to use role-based package selection for the Nginx APT
source?
That means using:
deb http://nginx.org/packages/debian/ *stable* nginx
deb-src http://nginx.org/packages/debian/ *stable* nginx
Instead of:
deb
The problem I see is you try to address the process of requests differently
whether from inside your network or from the outside.
You may already solve the problem of your outside interface easily with server
names http://nginx.org/en/docs/http/server_names.html (knowing how nginx
processes a
Pure wild guess:
Maybe a missing trailing slash in the request resulting in a temporary
redirection (and then processed again)?
Have you checked the requests made on the client side for any sign of
unwanted redirection? You could then use them to correct your rewrite
directive.
Hope I helped,
Hello,
I am trying to understand how fastcgi_read_timout works in Nginx.
Here is what I wanna do:
I list files (few MB each) on a distant place which I copy one by one
(loop) on the local disk through PHP.
I do not know the amount of files I need to copy, thus I do not know the
total amount of
looping internally - well performance-wise that is.
Steve
On Sun, 2013-05-26 at 21:31 -0400, B.R. wrote:
No ideas?
---
B. R.
On Sat, May 25, 2013 at 1:01 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
Hello,
I am trying to understand how fastcgi_read_timout works
Holdoway st...@greengecko.co.nzwrote:
Surely, you're still serialising the transfer with a loop?
On Sun, 2013-05-26 at 22:11 -0400, B.R. wrote:
Thanks for your answer.
I didn't go into specifics because my problem doesn't rely at the
application-level logic.
What you describe is what my
-26 at 22:38 -0400, B.R. wrote:
One way or another, even if an external script is called, PHP will
need to wait for the scripts completion, making the parallelization
impossible or at least useless (since, to wait for a return code of an
external script is still blocking).
I am
Hello Maxim,
I spent a lot of time trying to figure out what is happening.
It seems that after some service restart, the problem sometimes disappear
before coming back again on the following try.
I finally managed to capture the debug log you'll find as attachment. I'll
need your expertise on
Hello,
You might be interested in the following:
http://nginx.org/en/docs/http/configuring_https_servers.html#name_based_https_servers
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
I do not know if my private emails on the matter to Maxim went through.
Non-broken resources were included.
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I read :
With this configuration a browser receives the default server’s
certificate, i.e. www.example.com regardless of the requested server name.
This is caused by SSL protocol behaviour. The SSL connection is established
before the browser sends an HTTP request and nginx does not know the name
Hello,
On Wed, Jun 5, 2013 at 1:56 AM, shahzaib shahzaib shahzaib...@gmail.comwrote:
Hello,
We're using nginx-1.2.8 to stream large files size 1G but found the
slow stream with high utilization of harddrive using command iostat -x -d
3
Device: rrqm/s wrqm/s r/s
Hello,
On Sat, Jun 8, 2013 at 2:18 PM, Travis Maxwell the.energe...@gmail.comwrote:
Hi,
I'm using nginx with SSL, and I want to always redirect to www, regardless
of whether the request is http or https. I just want to redirect to the
respective protocol but with www.
I have the port 80
On Thu, Jun 13, 2013 at 4:51 PM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
On 13 June 2013 09:38, mailinglis...@simonhoenscheid.de wrote:
[snip]
RewriteRule ^favicon\.ico$ - [R=404,L]
location /(^favicon)/(.*\.(ico)) {
return 404;
Don't do that. You're only hurting yourself.
Hello,
On Fri, Jun 14, 2013 at 4:35 AM, mailinglis...@simonhoenscheid.de wrote:
Am 13.06.2013 19:35, schrieb B.R.:
What is the observed behavior?
The parameters are not given corectly to the php script, delivering the
picture.
What
does the script receive ? Details!
What do show
Hello,
On Thu, Jun 27, 2013 at 1:02 PM, Ben Johnson b...@indietorrent.org wrote:
On 6/27/2013 12:42 PM, Ben Johnson wrote:
I don't want PMA (anything within the /pma/ location) to be accessible
over a plaintext connection. In other words, I wish to force HTTPS.
Do I need to add
Hello again,
I resorted to the if control structure because, without it, the
browser became stuck in a redirect-loop. (The reason for this is
obvious.) Then again, I suppose that the redirect-loop would occur
regardless of whether I use a return 301 or rewrite.
How would you recommend
Your configuration means that Nginx is listening on port 80 and will
forward any request form example.com to a backend located on localhost
listening on port 8009.
Since Nginx is a proxy, you need a backend to serve content to which
requests sent to Nginx will be forwarded.
You seem not to
The question is: How does Nginx process a request made with an unknown
hostname?
The answer is: http://nginx.org/en/docs/http/request_processing.html
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Yup, include is the way I would do that personally.
Documentation: http://nginx.org/en/docs/ngx_core_module.html#include
The funny thing is you already are using the 'include' directive: look at
your 'include fastcgi_params;' line. There must be a 'fastcgi_params' file
in your configuration
Hello,
On Tue, Aug 13, 2013 at 8:31 AM, Ruslan Ermilov r...@nginx.com wrote:
If there's a single server, max_fails and fail_timeout parameters
are ignored, and such a server will never become temporarily down.
That would be worth mentioning in the Nginx documentation...
Hello,
On Tue, Aug 13, 2013 at 9:12 AM, Jaap van Arragon
j.vanarra...@lukkien.comwrote:
Hello,
I'am looking for a way to limit the number of connection in one hour to a
location named /api/
I've looked at the ngx_http_limit_conn_module module but I don't
understand how to limit the amount
I guess it would be nice if the doc warned about directives that need a
server restart to be reloaded.
Everyone supposes (as it seems obvious) that reloading Nginx is enough to
apply configuration changes.
An interesting part of the question was the inquiry about the potential
existence other
Hello,
On Sat, Aug 17, 2013 at 7:37 AM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
I don't think that calling nginx -t as a mandatory step before
configuration reload is a good idea: nginx binary running and
nginx binary on disk might be different, and nginx -t result
might be
This discussion started regarding concerns about the BREACH, which (if you
documented about it) attacks SSL-encrypted HTTP-level-compressed data, thus
implying the discussion around gzip.
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
Hello,
On Sun, Aug 18, 2013 at 3:14 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Making any changes to the configuration isn't something
significant: even without changes at all new binary on disk might
not consider an old configuration as a valid e.g. due to some
module not compiled in. And
On Mon, Aug 19, 2013 at 2:04 AM, Igor Sysoev i...@sysoev.ru wrote:
Incorrect.
CRIME attacks a vulnerability in the implementation of SSLv3 and TLS1.0
using CBC flaw: the IV was guessable. Hte other vulnerability was a
facilitator to inject automatically arbitrary content (so attackers
On Tue, Aug 20, 2013 at 5:12 PM, rmalayter nginx-fo...@nginx.us wrote:
No, the conclusion is: don't echo back values supplied by the requester as
trusted in your *application* code. This is the most basic of
anti-injection
protections. BREACH is the result of an application-layer problem, and
Hello,
On Wed, Aug 21, 2013 at 9:42 PM, cachito nginx-fo...@nginx.us wrote:
if ($http_cookie ~*
comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_logged_in) {
set $no_cache 1;
}
If the user sends requests using cookies from Wordpress, the cache won't
be used...
Thus, you
Hello,
On Wed, Aug 21, 2013 at 9:48 PM, Michael Kovacs kov...@gmail.com wrote:
Hey all,
I'm running nginx 1.2.6 from a packaged install on Ubuntu 13.04. I'm at a
total loss as to how this is happening but I simply cannot disable gzip
compression for my server no matter what I try. Setting
Hello,
Isn't there a dedicated nginx-ru mailing list? :o)
---
*B. R.*
**
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Absolute vs Relative paths.
The log file line says it all: '/webalizer/index.html' doesn't exist, which
is not the path of the file you wanna serve...
Take a look at the following examples showing how 'location' address is
replaced or completed (depending on absolute or relative 'alias'
Hello,
On Mon, Oct 7, 2013 at 5:35 PM, Francis Daly fran...@daoine.org wrote:
Run the fastcgi server like this:
env -i php-cgi -d cgi.fix_pathinfo=0 -q -b 9009
Use an nginx config which includes something like this:
I would recommend being careful about that experiment since there is
Hello,
I would take a look at this module:
http://nginx.org/en/docs/http/ngx_http_limit_conn_module.html
Official modules are available through the pre-compiled official binaries,
you won't need to do that by hand.
---
*B. R.*
___
nginx mailing list
Wow, that's maintenance ^^
Thanks to the dev team.
I am getting lost on the trac Web interface: where could I get details o
nthe defect affecting autoindex?
I'll wait for the Debian package to be available in the repo, then... :o)
---
*B. R.*
___
It's something a lot of people are bumping on.
401 HTTP covers both failed and missing authentication but isn't possible
for Nginx to differentiate those states and thus only generate an error
message on a failed (ie not empty credentials, either user or password
containing something) attempt?
Thanks Maxim!
I didn't really pay attention to the difference in the error messages.
Thanks for remembering them.
The question of the severity of the last message has no simple answer I'm
afraid, since it depends on the use case.
Maybe someone wishes to log any attempt to access a protected
IMHO, using a rewrite in nginx to modify the way PHP processes the request
looks strange to me. Maybe am I wrong.
Have you had a look in the content of the params you send to PHP through
CGI? Overloading some of the variables by removing the leading '/b' there
might help PHP resolving correctly
Hello,
On Sun, Nov 24, 2013 at 3:43 PM, Francis Daly fran...@daoine.org wrote:
On Sun, Nov 24, 2013 at 07:54:56AM -0500, Ian Evans wrote:
Hi there,
location ^~ /rather/ {
fastcgi_intercept_errors on;
fastcgi_pass 127.0.0.1:9000;
fastcgi_param HTTPS on;
Does it work if you remove
Hello,
Sometimes reading the documentation might help :
http://nginx.org/en/docs/control.html
If you look at your service file, you'll notice that a 'reload' means
sending SIGHUP to the master process for the particular case of nginx.
I'll leave the conclusion to you, assuming that the doc is
Hello,
On Wed, Dec 4, 2013 at 12:48 PM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
On 4 December 2013 09:36, Lukas Tribus luky...@hotmail.com wrote:
Agreed, the configuration workaround is viable; but the problem lies
in the actual troubleshooting. Coming to this conclusion takes
I am new to the use of maps, but I suppose it would fit perfectly, using
core variables such as the binary IP address:
Maybe something like:
server {
error_page 503 /503.html # Configuring error page
map $binary_remote_addr $target { # Configuring white-listed IP
addresses
Hello,
On Sat, Dec 7, 2013 at 4:10 PM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
rewrite ^.*$ $target #Redirecting all traffic according to
map-assigned
I don't particularly like ^^^ this. It seems like a level of
indirection too far ;-)
To me, your solution looks double
Hello,
On Sat, Dec 7, 2013 at 6:31 PM, Ian Evans ianev...@digitalhit.com wrote:
Thanks. I'll give this a spin. Is there anyway to still trigger the
mapping based on the existence of a maintenance.whatever file? Just
thinking of the ease of quickly touch'ing the maintenance file to trigger
On Sat, Dec 7, 2013 at 10:39 PM, itpp2012 nginx-fo...@nginx.us wrote:
Full working config;
http://www.cyberciti.biz/faq/custom-nginx-maintenance-page-with-http503/
Thanks for replying after having carefully read what is asked for by Ian
and not giving a too quick answer copy-pasted from
Try to understand what you are doing first.
One request is handled in one location.
For this request, the one location that you want to be used is not the
one that nginx actually uses.
1.
location / {
2.
location ~ \.php$ {
3.
location /phpmyadmin/ {
4.
location ~
It seems your syntax is obsolete. Have a look at
http://nginx.org/en/docs/http/converting_rewrite_rules.html where it is
explicitly written.
It is also explicitely wriiten on the wiki page you visited that the
resource is obsolete and that you should use
Hello,
On Fri, Jan 24, 2014 at 9:45 PM, Jeroen Ooms jeroen.o...@stat.ucla.eduwrote:
However, this bypasses the cache when either $http_cache_control OR
$is_get is set. How can I achieve to set proxy_cache_bypass when both
http_cache_control AND $is_get are set?
The logic you wish imply
I think what you both request is interesting.
However, I would like to push the analysis further.
Is seems SPDY design is flawed because it enables flexibility and offer new
features compared to HTTP without taking into account the very basis of a
protocol: being efficient by allowing quick and
Hi Valentin,
Thanks for that information.
However, since the usual way to do things is to have 2 branches: production
development, I guess the awaited people initial reaction is not to trust
the 'mainline' branch.
I think it would be highly beneficial to mention somewhere (on the
downloads
Don't forget taking into account browser buffering: depending on which one
you are using, it waits for a certain amount of data before displaying
anything.
To convince you of that, listen to the incoming network traffic to check
that data is arriving to the client.
That's a limit upon you cannot
Right, I did not pay attention to that.
However, when requesting the root (by typing b.cd in the browser), $uri
should be empty, thus why can't '$uri/' act as '/' and redirect accordingly?
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
Thanks for you time, Francis.
I understand the loop cycles (and thanks for the clarification about $uri
content).
If I may, there is still a little something bothering me:
The condition required for a loop to be created is that $uri (= /) doesn't
match any file, thus redirecting and trying
Sorry for my fluffy terminology.
What I called 'error handler' was the final argument of the try_files
directive, the one used if any other one fails to detect a valid
file/directory.
We ended concluding that:
try_files $uri $uri/; was invalid, looping internally for an infinite
amount of time
Thanks for your help, Francis!
That's an amazingly detailed explanation. The differences in behavior
between 'normal' arguments and the last one are the key but the doc does
not (cannot?) go into details about them.
---
*B. R.*
___
nginx mailing list
Despite what you are stating, I see a valid NZ IP address in the
'$_SERVER' environment variables of the PHP instance running behind Nginx
(most probably 210.55.x.x prefix).
The Apache remote address is not the right one.
Since you failed to explain your setup, I suppose Nginx proxies traffic
I am tempted to copy an URL recently provided by Maxim in another thread:
http://www.catb.org/~esr/faqs/smart-questions.html
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
I am considering the following configuration:
server {
include fastcgi.conf # Default configuration coming with a Debian
package which contains a definition of the SCRIPT_FILENAME FastCGI variable
with $document_root$fastcgi_script_name as its value
...
location ~^/index\.php {
Hello Francis and Maxim,
I understand very well that $fastcgi_script_name value is defined after
fastcgi_split_path_info is called.
However I was wondering about other variables which value depend on
$fastcgi_script_name, for example when PHP's SCRIPT_NAME has been defined
in the already included
On Tue, Feb 25, 2014 at 2:49 AM, Maxim Dounin mdou...@mdounin.ru wrote:
Note (quote from http://nginx.org/r/fastcgi_param):
: These directives are inherited from the previous level if and only
: if there are no fastcgi_param directives defined on the current
: level.
There are
On Mon, Mar 3, 2014 at 10:11 PM, talkingnews nginx-fo...@nginx.us wrote:
This page http://wiki.nginx.org/PHPFcgiExample says
This guide run fine on php.ini cgi.fix_pathinfo = 1 (the default). Some
guide insist to change it to cgi.fix_pathinfo = 0 but doing that make
PHP_SELF variable
For testing the new binary and being able to revert quickly to the other
one, use the advice on this documentation page:
http://nginx.org/en/docs/control.html
That way, you will have virtually no downtime and only stop the old nginx
process when you decide the new one is doing its job.
---
*B.
This ML is intended for nginx-related problems. Yours is PHP-related.
Either ask this question on some PHP ML or
RTFMhttp://www.php.net/manual/en/faq.obtaining.php#faq.obtaining.threadsafety
...
With regards,
---
*B. R.*
___
nginx mailing list
Hello,
On Tue, Mar 18, 2014 at 8:18 PM, Haris Bogdanovich fbogdano...@xnet.hrwrote:
How to get started with nginx ?
First of all, welcome to nginx community :o)
All the basic principles can be found there:
http://nginx.org/en/docs/beginners_guide.html
Is there some tutorial for
Have you tried to 'reload' the server by sending SIGHUP to the master
process? Or if this is not enough try upgrading it on the fly or restart
(stop/start) it.
Nginx, as any process, cannot detect system changes such as this ones on
its own...
If you modiify your hardware environment, you need to
I am using the official Debian package (stable) and I noticed the service
file, in its do_stop() function, sends SIGTERM to the master process.
However, the docs say SIGTERM (and SIGQUIT) sent to the master process
provokes a 'fast shutdown' whereas SIGQUIT would provoke a 'graceful
shutdown'.
Thanks Igor for that clear and concise answer!
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Nginx binds file extensions with file types:
http://nginx.org/en/docs/http/ngx_http_core_module.html#types
An examples there links to
http://nginx.org/en/docs/http/ngx_http_core_module.html#default_type
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://forum.nginx.org/ fails to return proper content.
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Still down from my side. I do not have cache anywhere, since my browser
purges it on every shutdown.
If you look at your frontend logs around the time I specified in the
subject, you should notice some 502 being thrown. Do you really need my IP
address? Any 502 you would find under
Attachment, attachment...
---
*B. R.*
http_exchange
Description: Binary data
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Thanks Jonathan for the pointer. I was going to throw some WIkipedia page
about it but RFC is definitely the best!
I am glad you discovered I was not alone Jim, thought I am a little sad
that you were that harsh welcoming my input as, if I may, I also did the
reporting on my free time, and
Wow Francis.
You are a patient man. I love the way you teach things. I mean it all.
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
In nginx, you have the http_header name embedded variable in the core
module http://nginx.org/en/docs/http/ngx_http_core_module.html#variablesto
access HTTP headers.
You can build the logic the way you want (through
maphttp://nginx.org/en/docs/http/ngx_http_map_module.htmlor
directives from the
On Wed, Apr 2, 2014 at 11:11 AM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
As an aside, IIRC people @nginx have stated publicly that post_action is a
hack, and that its behaviour should not be relied on. I'm without Internets
right now so can't find you the quote, but it was sufficient
I would use:
- rewrite directives only at server level, no need for location here
- a single regex with OR logic to match both the advancedsearch and the
profile URI since the rewriting grammar is the same
- a single regex for both 'index.php' rewritings, since the grammar of
category+page is the
Nginx can proxy HTTP requests to backend through the proxy module
directiveshttp://nginx.org/en/docs/http/ngx_http_proxy_module.html
.
If your backend is able to handle those requests on its own (ie if it is
able to handle connections without any webserver), then make nginx as a
load-balancer
I have little knowledge about Windows, but I know that the SYSTEM account
is usually related to processes running as services.
SYSTEM has restricted rights on number of things, despite appearing as a
'super-account', an attempt from Windows to mitigate services
'super-powers'.
It would not
As the location
docshttp://nginx.org/en/docs/http/ngx_http_core_module.html#locationspecifies,
the solution you provided should work.
Ensure that:
1°) You are working with the right binary
2°) Configuration syntax is correct (nginx -t) and reload was successful
(no message in that direction in
I do not know about caching nor do I take it into consideration as it is
not part of the problem as stated.
You stated that the location regex was the problem and you seem to have
taken the proper checks to verify the proper location is being used, hence
I assume the location regex is not the
There is not much to learn from a gujide that what has alrfeady been said
on http://heartbleed.com.
More specifically, there is nothing related to nginx nor SPDY...
Heartbleed is related to OpenSSL and the solution is either to update your
OpenSSL version/package with the official/your distro
Quick sidenote, not scratching the surface of your problem:
I would have posted on ServerFault, not StackOverflow
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Rather than posting raw outputs, try to understand the piece orf advice
Maxim gave to you.
I suspect those SSL-validation websites test websites... which correspond
to a certain standard port.
I see a problem, don't you ?
---
*B. R.*
___
nginx mailing
Using http://lmgtfy.com/?q=PEM+routines%3APEM_read_bio%3Abad+end+line
I found http://drewsymo.com/2013/11/fixing-openssl-error/
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Igor and Maxim positions, I suppose, are based on the fact that, unless
using an external system to authenticate the user of a certificate, storing
both certificate + passphrase on thel same system, accessed by the same
user (the one running nginx which loads the certificate and needs to
decrypt
Logs?
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, May 6, 2014 at 8:39 PM, dcaillibaud nginx-fo...@nginx.us wrote:
2) (I guess E but I'm not so sure), this can also be a pitfall
example (how
complicating things can lead to unexpected behaviour)
location /images/ {
location ~* \.(gif|jpg|jpeg)$ {
[
I request all Nginx master/experts to help me.
That looks like an odd way to *ask* for help.
If you wanna *request* help, consider getting paid support. But even doing
that, that is rude...
What the error says is that the '*backend* closed connection
prematurely'... You should look into it
I just saw something strange on http://nginx.org/en/security_advisories.html
:
An error log data are not sanitized
Severity: none
CVE-2009-4487 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4487
Not vulnerable: none
Vulnerable: all
Severity is labelled as 'None', though the CVE talks,
I read the StackOverflow thread and it seems there are 2 teams ping-ponging
the problem:
- One says that it is a terminal problem and that control and escape
sequences should not be executed
- The other says that those features are userful and say that log files are
supposed to be text-only, thus
Quick question:
Are hardcoded default error pages being cached when *_cache directives
specify their HTTP error code? Or does it only apply to pages specified
with the error_page directive?
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
Those modules seem to be part of nginx since
0.8http://forum.nginx.org/read.php?27,134561,134561#msg-134561but I
could not find any docs on the uwsgi module on the official website.
Why that?
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
1 - 100 of 375 matches
Mail list logo
