Hi,
On 2018-09-25 20:32, Lahiru Prasad wrote:
> What is the best way to cache POST requests in Nginx. I'm familiar
> with using redis module to cache GET requests. But is it possible to
> use the same for POST ?
It's possible to cache POST-requests, but it's generally not something
you want
> but https://15.15.15.15/ throw error "Not found: The requested URL / was not
> found on this server. ", And I can not find the error. This is the
> configuration:
> and urls.py django:
>
> urlpatterns = [
> path('', RedirectView.as_view(url='/inicio/', permanent=True)),
>
I've also tried adding "/" and throwing the same error. I have also added to
the .conf file:
location = / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
}
before the fragment location / {..} with the same error.
This error is very strange. The
> On 25 Sep 2018, at 16:35, Palvelin Postmaster via nginx
> wrote:
>
> I use Wordpress’ REST API post feed to embed articles on an external site. My
> articles are updated fairly seldom, so there’s probably no need to
> dynamically compile every request response. I’m thinking of using
Changes with nginx 1.15.425 Sep 2018
*) Feature: now the "ssl_early_data" directive can be used with OpenSSL.
*) Bugfix: in the ngx_http_uwsgi_module.
Thanks to Chris Caputo.
*) Bugfix: connections with some gRPC backends might not be
I use Wordpress’ REST API post feed to embed articles on an external site. My
articles are updated fairly seldom, so there’s probably no need to dynamically
compile every request response. I’m thinking of using fastcgi cache to cache
the feed.
I’m currently skipping caching for all requests
Hello Nginx users,
Now available: Nginx 1.15.4 for Windows https://kevinworthington.com/
nginxwin1154 (32-bit and 64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Hi,
What is the best way to cache POST requests in Nginx. I'm familiar with
using redis module to cache GET requests. But is it possible to use the
same for POST ?
Search showed that Nginx POST caching possible via disk cache. I'm thinking
whether it would be a good idea to use a RAM disk for
Привет!
Продолжаю свой вопрос про построение динамического бинарника и
использование для этого add_afer_body и njs
> http://mailman.nginx.org/pipermail/nginx-ru/2018-September/061454.html
> http://mailman.nginx.org/pipermail/nginx-ru/2018-September/061461.html
В итоге сейчас собрали такую
details: http://hg.nginx.org/nginx/rev/dcd9303b0d73
branches:
changeset: 7363:dcd9303b0d73
user: Maxim Dounin
date: Tue Sep 25 18:11:39 2018 +0300
description:
release-1.15.4 tag
diffstat:
.hgtags | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs (8 lines):
diff
details: http://hg.nginx.org/nginx/rev/49d498356538
branches:
changeset: 7362:49d498356538
user: Maxim Dounin
date: Tue Sep 25 18:11:39 2018 +0300
description:
nginx-1.15.4-RELEASE
diffstat:
docs/xml/nginx/changes.xml | 90 ++
1 files
Changes with nginx 1.15.425 Sep 2018
*) Feature: now the "ssl_early_data" directive can be used with OpenSSL.
*) Bugfix: in the ngx_http_uwsgi_module.
Thanks to Chris Caputo.
*) Bugfix: connections with some gRPC backends might not be
Изменения в nginx 1.15.4 25.09.2018
*) Добавление: теперь директиву ssl_early_data можно использовать с
OpenSSL.
*) Исправление: в модуле ngx_http_uwsgi_module.
Спасибо Chris Caputo.
*) Исправление: соединения к некоторым
Изменения в nginx 1.15.4 25.09.2018
*) Добавление: теперь директиву ssl_early_data можно использовать с
OpenSSL.
*) Исправление: в модуле ngx_http_uwsgi_module.
Спасибо Chris Caputo.
*) Исправление: соединения к некоторым
details: http://hg.nginx.org/nginx/rev/c09c7d47acb9
branches:
changeset: 7361:c09c7d47acb9
user: Maxim Dounin
date: Tue Sep 25 14:00:04 2018 +0300
description:
SSL: logging level of "no suitable signature algorithm".
The "no suitable signature algorithm" errors are reported by
details: http://hg.nginx.org/nginx/rev/8f25a44d9add
branches:
changeset: 7360:8f25a44d9add
user: Maxim Dounin
date: Tue Sep 25 13:59:53 2018 +0300
description:
SSL: logging level of "no suitable key share".
The "no suitable key share" errors are reported by OpenSSL 1.1.1 when
using
16 matches
Mail list logo