Есть довольно сложный сайт, запутанная внутренняя логика которого
препятствует нормальному включению кеширования на уровне nginx. Разработчик
выделил все неизменяемые блоки контента под отдельный URI, которые инклюдит
их шаблона страницы через SSI. Пытаюсь для локейшена с этими блоками
включить
Переформулируя вопрос: можно ли как-то выделить в локейшене запросы, которые
надо кешировать, пропуская все остальные напрямую к движку? То есть, нужна
логика, обратная директиве proxy_cache_bypass. Пока придумал только одно:
устанавливать переменную для всех запросов, в нужном локейшене её
On Wednesday 04 June 2014 06:13:38 RedRat wrote:
Переформулируя вопрос: можно ли как-то выделить в локейшене запросы, которые
надо кешировать, пропуская все остальные напрямую к движку? То есть, нужна
логика, обратная директиве proxy_cache_bypass. Пока придумал только одно:
устанавливать
А зачем их выделять в одном location-е? Заведите отдельный location,
где будет включено кэширование и куда будут попадать все запросы,
которые необходимо кэшировать.
Все запросы к движку попадают в один именованный локейшен. Если выделять ещё
один или несколько локейшенов под запросы, которые
On Wednesday 04 June 2014 06:43:31 RedRat wrote:
А зачем их выделять в одном location-е? Заведите отдельный location,
где будет включено кэширование и куда будут попадать все запросы,
которые необходимо кэшировать.
Все запросы к движку попадают в один именованный локейшен. Если выделять
Здравствуйте!
Подскажите пожалуйста, на сайте domain.ru с ip 1.1.1.1 стоял apache 2.2 и
Joomla 1.5 и в конфиге были такие строки
ProxyRequests On
ProxyVia Block
AllowCONNECT 21 25 110 443 22 554 563 5190 1080 8080 5140 5160 4000 1478
1479 1480 8008 1480
Proxy *
Order deny,allow
deny from all
On 4 June 2014 05:48, Vishal Mestri vishal.mes...@cloverinfotech.com wrote:
Hi Jonathan Matthews,
Thank you for your valuable comments.
I understand , what you would like to suggest, but we are using self-signed
certificate just for trial demo.
Once UAT is done, we would be using actual
Hi,
I'm using ssl_client_certificate, I want to set proxy_set_header X-Cert-DN
$ssl_client_s_dn; when I proxy.
I've ssl_verify_client set to optional - this all works great, but in the
browser, the user gets a cert prompt. Is there a way I can avoid the cert
prompt - so the header will get set
I needed to use modsecurity so I compiled nginx and modsecurity.
Modsecurity was compiled with options: ./configure
--enable-standalone-module
nginx with: ./configure
--add-module=../modsecurity-2.8.0/nginx/modsecurity/
When I try to test my configuration I have this:
[root@nginx1 nginx]#
Hi,
I am new to nginx and linux.
I tried to install nginx form source (nginx+rtmp module) following many
tutos on my Debian
And all gives me the same error:
./configure --add-module=../nginx-rtmp-module-master
make -f objs/Makefile make[1]: entrant dans le répertoire «
/root/nginx/nginx-1.4.3 »
Hi,
How to install Nginx from source and avoid the OpenSSL Bug ?
What openssl bug are you talking about? Debian contains all
important fixes afaik.
It seems error comes from :
Planned removal of SSL_OP_MSIE_SSLV2_RSA_PADDING breaks dependent software
if you are using OpenSSL 1.0.2 or
On Wed, Jun 4, 2014 at 3:33 PM, Lukas Tribus luky...@hotmail.com wrote:
How to install Nginx from source and avoid the OpenSSL Bug ?
What openssl bug are you talking about? Debian contains all
important fixes afaik.
I think 'yarek'
tries to build nginx with a 3rd-party program.
I'd
Hi,
How to install Nginx from source and avoid the OpenSSL Bug ?
What openssl bug are you talking about? Debian contains all
important fixes afaik.
I think 'yarek' tries to build nginx with a 3rd-party program.
Just installing libssl-dev from the debian repository would have
been
Hello!
On Tue, Jun 03, 2014 at 02:08:36PM -0700, Jayadev C wrote:
The problem is ngx_http_proxy doesn't do that either, once
rewrite is applied the url remains decoded (or I am not reading
the code correctly).
The proxy does ngx_escape_uri() if URI was rewritten. It has to,
as unencoded
I think this bug was fixed in nginx_refactoring tree.
On Wed, Jun 4, 2014 at 7:00 PM, Robert Paprocki
rpapro...@fearnothingproductions.net wrote:
Can you post a full core dump? Did you verify the mod_security tarball
you downloaded? Can detail the steps taken to build that module? What
Can you post a full core dump? Did you verify the mod_security tarball
you downloaded? Can detail the steps taken to build that module? What
version of nginx are you trying to build?
On 6/4/2014 06:27, Kurt Cancemi wrote:
Hello, this is unrelated to nginx and has to do with mod_security.
Andrei, have you checked issue 630?
https://github.com/SpiderLabs/ModSecurity/issues/630
On Wed, Jun 4, 2014 at 7:12 PM, Andrei Belov de...@nginx.com wrote:
Hi,
there is a lot of open issues with ModSecurity and nginx:
Hi all,
How can I make sub-request to external resource (without returning it to
the user)?
The following commands are used only for internal resources:
ngx.location.capture
ngx.exec
any idea? :-)
Thanks in advance,
___
nginx mailing list
@itpp, i just used your method try_files and it worked flawlessly :).
Following is the testing config :
server {
listen 80;
server_name domain.com;
root /var/www/html/files;
location / {
root /var/www/html/files;
try_files $uri @getfrom_origin;
}
Also sync to a temp folder and move after completion or nginx will attempt
to send partial files.
Oh right. Thanks for quick help and suggestion :). I'll look into wanproxy
now.
On Thu, Jun 5, 2014 at 12:19 AM, itpp2012 nginx-fo...@nginx.us wrote:
shahzaib1232 Wrote:
I use nginx 1.7.1 as frontend proxy to Apache 2.2.27 + php-fpm 5.5.13.
When I add new domain, then just reload nginx it throwing errors like
connection reset etc.
Error log is full of something like this:
tail -f /var/log/nginx/error.log
2014/06/04 11:36:23 [alert] 12928#0: worker process 3958
Also dmesg is full of this:
nginx[9184]: segfault at 27 ip 00447606 sp 7fff9972a8b0 error 4
in nginx[40+b6000]
nginx[9599]: segfault at 19 ip 00447606 sp 7fff9972b7f0 error 4
in nginx[40+b6000]
nginx[9579]: segfault at 117 ip 00447606 sp 7fff9972b7f0
Hey,
assuming this is your whole config, could you either uncomment the
access_log directive or add access_log off? I'm pretty sure you're
hitting the bug introduced in 1.7.0:
http://mailman.nginx.org/pipermail/nginx-devel/2014-June/005430.html
Best regards,
Piotr Sikora
On 04.06.2014 23:37, Spacedust wrote:
Also dmesg is full of this:
nginx[9184]: segfault at 27 ip 00447606 sp 7fff9972a8b0 error 4
in nginx[40+b6000]
nginx[9599]: segfault at 19 ip 00447606 sp 7fff9972b7f0 error 4
in nginx[40+b6000]
nginx[9579]: segfault at 117 ip
Piotr Sikora Wrote:
---
Hey,
assuming this is your whole config, could you either uncomment the
access_log directive or add access_log off? I'm pretty sure you're
hitting the bug introduced in 1.7.0:
support Wrote:
---
yes.
update and test
02.06.2014 10:24, wishmaster пишет:
I have the same problem in my php-application. Admin folder is
protected with auth_basic and the rest folders - without auth. I have
not found any solution
Jonathan Matthews Wrote:
---
Fortunately, this being a *public* *mailing* *list*, and Francis
(along with almost every other subscriber) giving his time, experience
and opinions for free, you are definitely no worse off than when you
started.
27 matches
Mail list logo
