Hi!
Both 'greater' and 'less' are not the lowest priority operations,
we may make a litter improvement as following.
diff -r 29ba1d6a2da9 src/core/ngx_core.h
--- a/src/core/ngx_core.h Tue Apr 04 18:01:57 2017 +0300
+++ b/src/core/ngx_core.h Fri Apr 28 11:27:41 2017 -0400
@@ -97,8 +97,8 @@
My guess would be that your app is redirecting back to the slash urls
Your could test this with a directory on the webserver that has a
matching index file.
Alternatively point a browser at the upstream and check for redirects
directly
On 28/04/2017 17:52, Alex Med wrote:
Steven -
I
Hello!
I’m new to nginx, playing using the api and making some handlers and filters.
Now what i would like to do is to
process the request headers, call an external c library, do some work and pass
the request to an upstream using proxy_pass.
I read about http request processing phases and
Its part of stream {}
http://mailman.nginx.org/pipermail/nginx-devel/2016-September/008752.html
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,273859,274018#msg-274018
___
nginx mailing list
nginx@nginx.org
Chad,
On 5/1/2017 1:05 PM, Chad Hansen via nginx wrote:
Bumping; does anyone have experience using upstream_bytes_sent or
upstream_byes_received?
nginx: [emerg] unknown "upstream_bytes_sent" variable
nginx: configuration file /etc/nginx/nginx.conf test failed
It's unclear to me
Пардоньте, HA-Proxy косячил запросы... удалите тему
Posted at Nginx Forum:
https://forum.nginx.org/read.php?21,274011,274015#msg-274015
___
nginx-ru mailing list
nginx-ru@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-ru
Лог nginx
2017/05/01 17:54:30 [error] 20248#0: *27 SSL_do_handshake() failed (SSL:
error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:SSL alert
number 48) while SSL handshaking to upstream, client: ip-client, server:
server-in-inet, request: "POST / HTTP/1.1", upstream:
server {
listen 443;
server_name server-in-inet;
access_log /var/log/nginx/subscription-access.log main;
error_log /var/log/nginx/subscription-error.log warn;
proxy_set_headerX-Real-IP $remote_addr;
proxy_set_headerX-Forwarded-For
Всем доброго дня!
Есть VPN сервер и VPN клиент. Туннель между ними успешно поднимается, пинги
ходят как по IP так и по DNS.
Конфиг NGINX:
server {
listen 80;
server_name xxx-xxx.me;
proxy_set_headerX-Real-IP $remote_addr;
On Mon, May 01, 2017 at 01:50:10PM +0200, Lucas Rolff wrote:
Hi there,
Thanks for the extra explanation. It is clear to me now.
> When I access https://minio.box.com// Minio will generate an
> XML containin a list of objects within a specific bucket (as per S3
> API standards).
>
> Example:
Hi Francis,
Thanks for your reply.
A little about what I'm doing/trying to make work.
I use Minio (https://www.minio.io/) - which is a S3 compatible object
storage server - it's a simple Go binary, that you pass an argument,
simply a directory which you want to store your buckets and files
On Sun, Apr 30, 2017 at 10:44:21AM +, Lucas Rolff wrote:
Hi there,
> I have a small scenario where I have a backend (s3 compatible storage), which
> by default generates a directory listing overview of the files stored.
> I want to be able to serve an "index.html" file if the file exists,
Всем доброго дня. В связи с переездом сайта на новое железо решил в
появившееся время пересмотреть конфиги и вспомнил об одном "костыле" который
так и не переделал.
Итак часть конфига:
location /gzipper { #сжималка статичных файлов
internal;
#Тут происходить создание .gz версии.
Dothris писал 2017-05-01 12:05:
Добрый день!
Добрый день, Dothris!
В логах Nginx
2017/05/01 08:32:06 [error] 27245#0: *7 SSL_do_handshake() failed (SSL:
error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:SSL
alert
number 48) while SSL handshaking to upstream, client:
# HG changeset patch
# User Matwey V. Kornilov
# Date 1492936703 -10800
# Sun Apr 23 11:38:23 2017 +0300
# Branch fsize
# Node ID 0d6c509169a32624cce431f2469b10b4f961510e
# Parent 5116cfea1e9a84be678af10e0ff1f1fce9b00cfb
SSI: implemented "fsize" SSI command.
diff
Добрый день! Подскажите пожалуйста, как сделать Nginx как SSL клиент?
nginx version: nginx/1.8.1
Ниже конфиги nginx.
server {
listen 80;
server_name roga-and-kopyta;
access_log /var/log/nginx/access.log main;
error_log
16 matches
Mail list logo