Valentin V. Bartenev Wrote:
---
> This issue should be reported to Safari. It appears that it doesn't
> handle refused streams.
>
> I'm going to make a workaround, but it will take time.
Just to clarify: this issue also affects Firefox 45.
Hello Giulio,
I can help you out with nginx configuration, optimisation and security
auditing. I was setting up nginx-based servers and converting from Apache
configurations since 2009. I also have broad expertise with different linux
distributions.
If interested, mail me at l...@andrews.lv.
Valentin V. Bartenev Wrote:
> This issue should be reported to Safari. It appears that it doesn't
> handle refused streams.
>
> I'm going to make a workaround, but it will take time.
Thank you Valentin!
Let me know when the workaround is in the trunk so I could get it form the
repository and
Sorry, this is version of nginx obtained directly from GIT master branch. I
believe in the sense of described behaviour, it is essentially the same as
1.10.0.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,266525,266533#msg-266533
___
Hello,
As of recently, shortly after updating nginx to version 1.11.0, we started
getting the following errors in the error log for our sites configured with
HTTP/2 and SSL:
2016/04/29 14:54:12 [info] 22321#22321: *290 client sent stream with data
before settings were acknowledged while
I experience the same issue, but I do not have the module reported by
anonymous user installed:
system:~#nginx -t
Floating point exception
dmesg:
[659221.307369] traps: nginx[20028] trap divide error ip:422fba
sp:7ffd8c72a8a0 error:0 in nginx[40+95d000]
Posted at Nginx Forum:
It crashes with pagespeed module now. 1.9.10 was working fine.
Andrejs.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264422,264436#msg-264436
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Joó Ádám Wrote:
---
> The TLS extension is the only method to implement Certificate
> Transparency without the assistance of the CA, and starting with
> January 1 2015 Chrome refuses to display the green bar for EV
> certificates without
I am sorry, I found the answer to my own question:
HTTP/2 uses SPDY as a jumping-off point. HTTP/2, however, uses a fixed
Huffman code-based header compression algorithm, instead of SPDY's dynamic
stream-based compression. This helps to reduce the potential for attacks on
the protocol.
Posted at
How about this:
server {
listen 80;
server_name *.mydomain.com;
return 301 https://$http_host$request_uri;
}
Andrejs
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,261751,261762#msg-261762
Maxim,
How is compression of headers taking place when using the new http_v2
module? Does "spdy_headers_comp" directive have any replacement in the
http_v2 module? I looked at the source code but couldn't find any info.
Are headers compressed by default now?
Andrejs
Posted at Nginx
Hello Maxim,
Maxim Dounin Wrote:
---
As already replied in russian list, currently (going to be fixed)
this may be done only with a hack like
geo $x {
default ${include_path}:/my/other/include/path;
}
Странно, но абсолютно ничего. Я бы написал если бы было чего.
error_log /var/log/nginx/cm.error_log info;
Андрей
Posted at Nginx Forum:
http://forum.nginx.org/read.php?21,242399,242404#msg-242404
___
nginx-ru mailing list
nginx-ru@nginx.org
/var/log/cm.access_log:
191.128.53.162 - - [01/Sep/2013:12:54:52 +0200] GET
Забыл сообщить, что использую concat module
https://github.com/alibaba/nginx-http-concat для конкатенации Javascript/CSS
файлов в один запрос.
Андрей
Posted at Nginx Forum:
http://forum.nginx.org/read.php?21,242399,242407#msg-242407
___
nginx-ru
Это единственный сервер для listen 80?
Нет.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?21,242399,242409#msg-242409
___
nginx-ru mailing list
nginx-ru@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-ru
(Request-Line) GET
Oleksandr V. Typlyns'kyi Wrote:
Как видно из кода стороннего модуля(а туда тоже следовало бы
посмотреть),
там несколько return NGX_HTTP_BAD_REQUEST без записи чего-либо в лог
ошибок.
И они явно намекают на content type который теперь
application/javascript.
Добавление его в
Наблюдаю интересную картину. При длинном $uri (адресной строка = 750
символов) nginx 1.5.4 выдает 400 Bad Request, в то время как nginx 1.5.3 не
выдаёт ошибок и показывает страницу как полагается.
значение large_client_header_buffers в конфигурации в обоих случаях:
large_client_header_buffers 4
I would suggest not to use any ready-to-use-conversion-tools but rather
learn the differences and convert the hosts manually one by one. It took me
a couple of days to convert all of our sites to nginx and two weeks more to
realize the differences of Apache and Nginx handling very specific cases,
Yes, location is better and even faster in general.
Andrejs
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238002,238866#msg-238866
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
21 matches
Mail list logo
