Hi,
Currently the webdav module writes the request body to a temporary file
and moves it to destination filepath once upload is complete.
The patch below introduces dav_request_buffering. Default is "on". If
"off", the request body will be written directly to destination filepath
(unless destinat
If this actually yields a decrease in start time while not introducing
other effects we would use it. Our start time of a couple minutes is
annoying at times.
On Fri, Jun 2, 2017 at 3:57 AM, Andrew Borodin wrote:
> 2017-06-01 22:39 GMT+05:00 Maxim Dounin :
> > Thanks, though suggested change wil
Hey Valentin,
> The new initial window size can be lower than the previous one,
> so the difference can be negative (that's why the delta parameter
> of ngx_http_v2_adjust_windows() is ssize_t).
Oops, good catch, thanks!
Funnily enough, the original patch worked just fine (at least on
systems wh
# HG changeset patch
# User Piotr Sikora
# Date 1493067070 25200
# Mon Apr 24 13:51:10 2017 -0700
# Node ID 26c9e95a73295a344d39ac5e6d62787d26989c82
# Parent e00ba13ce421685981db6a98831409a234cc1e62
HTTP/2: don't send SETTINGS ACK before already queued DATA frames.
Previously, SETTINGS ACK
# HG changeset patch
# User Piotr Sikora
# Date 1493067147 25200
# Mon Apr 24 13:52:27 2017 -0700
# Node ID d61e944f55e70a5a25c8a79bfc5c167b7f22d62e
# Parent 1738ed9658e2a9a12370f4c828761a9fd058935d
HTTP/2: send SETTINGS ACK after applying all SETTINGS params.
This avoids sending unnecessar
# HG changeset patch
# User Piotr Sikora
# Date 1493067124 25200
# Mon Apr 24 13:52:04 2017 -0700
# Node ID 1738ed9658e2a9a12370f4c828761a9fd058935d
# Parent ab6ef3037840393752d82fac01ea1eb4f972301c
HTTP/2: emit new frames only after applying all SETTINGS params.
Previously, new frames coul
# HG changeset patch
# User Piotr Sikora
# Date 1493067017 25200
# Mon Apr 24 13:50:17 2017 -0700
# Node ID e00ba13ce421685981db6a98831409a234cc1e62
# Parent d61e944f55e70a5a25c8a79bfc5c167b7f22d62e
HTTP/2: make SETTINGS ACK frame reusable.
Signed-off-by: Piotr Sikora
diff -r d61e944f55e7
2017-06-01 22:39 GMT+05:00 Maxim Dounin :
> Thanks, though suggested change will certainly modify current
> nginx (documented) approach of searching for minimum possible
> hash sizes.
>
> It might be a better solution for large hashes though, as
> currently optimized by using a larger start size:
>
On Thursday 01 June 2017 17:48:25 Valentin V. Bartenev wrote:
> On Monday 24 April 2017 15:48:23 Piotr Sikora via nginx-devel wrote:
> > # HG changeset patch
> > # User Piotr Sikora
> > # Date 1493073310 25200
> > # Mon Apr 24 15:35:10 2017 -0700
> > # Node ID 07adf0a7009c3244de4b795c0c06927f
On Monday 24 April 2017 15:48:26 Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1493073310 25200
> # Mon Apr 24 15:35:10 2017 -0700
> # Node ID 3624fa075acac110a08c0f1c928c545a58c5801f
> # Parent b8d7f4a4d5abb4a27a772910358e263d49c618ef
> HTTP/2: do
On Monday 24 April 2017 15:48:25 Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1493073310 25200
> # Mon Apr 24 15:35:10 2017 -0700
> # Node ID b8d7f4a4d5abb4a27a772910358e263d49c618ef
> # Parent a8cfd4c454ff5433629bfd16444c6c71ee932fa1
> HTTP/2: ma
Hello!
On Thu, Jun 01, 2017 at 04:54:50PM +0500, Andrew Borodin wrote:
> Hi, Maxim!
>
> 2017-05-30 18:01 GMT+05:00 Maxim Dounin :
> >
> > The maximum size of hash table as specified by the hinit->max_size
> > field is indeed maximum size, and not the size of the hash table.
> > Following code in
On Monday 24 April 2017 15:48:24 Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1493073310 25200
> # Mon Apr 24 15:35:10 2017 -0700
> # Node ID a8cfd4c454ff5433629bfd16444c6c71ee932fa1
> # Parent 07adf0a7009c3244de4b795c0c06927f4316a87f
> HTTP/2: se
# HG changeset patch
# User Nate Karstens
# Date 1496332963 18000
# Thu Jun 01 11:02:43 2017 -0500
# Node ID cb09937f63834ab74b49a76b9b158dd0a5871309
# Parent 7aa7771191d61ef635478460017446bca1f6db55
PSK: add PSK identity variable
Adds the variable $ssl_psk_identity to get the PSK identity
# HG changeset patch
# User Nate Karstens
# Date 1496332865 18000
# Thu Jun 01 11:01:05 2017 -0500
# Node ID 7aa7771191d61ef635478460017446bca1f6db55
# Parent a38066b79d71b6ecb62a9f7618afe2cf3ed8a4f9
PSK: add configuration directives
Adds the directive "ssl_psk_dir" to the ngx_http_ssl_modu
Greetings,
I'm about push 3 patches that add support for PSK TLS cipher suites to nginx
and thought it would be good to discuss the feature itself in a separate thread.
First, PSK support is useful in certain environments that are not conducive to
a full public key infrastructure. The environme
# HG changeset patch
# User Nate Karstens
# Date 1496332504 18000
# Thu Jun 01 10:55:04 2017 -0500
# Node ID a38066b79d71b6ecb62a9f7618afe2cf3ed8a4f9
# Parent 716852cce9136d977b81a2d1b8b6f9fbca0dce49
PSK: make server certificates optional
Adds the directive "ssl_nocert" to the ngx_http_ssl_
On Monday 24 April 2017 15:48:23 Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1493073310 25200
> # Mon Apr 24 15:35:10 2017 -0700
> # Node ID 07adf0a7009c3244de4b795c0c06927f4316a87f
> # Parent 2c4dbcd6f2e4c9c2a1eb8dc1f0d39c99975ae208
> HTTP/2: em
details: http://hg.nginx.org/nginx/rev/716852cce913
branches:
changeset: 7020:716852cce913
user: Roman Arutyunyan
date: Thu Jun 01 15:44:23 2017 +0300
description:
Configure: disabled IP_PKTINFO feature on certain platforms.
On Cygwin and NetBSD 7.0+ struct in_pktinfo has no ipi_spe
Hello!
On Wed, May 31, 2017 at 01:54:00PM -0700, Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1496263895 25200
> # Wed May 31 13:51:35 2017 -0700
> # Node ID 057ec63be834988b6435b4ef64a1c3bd0cc23959
> # Parent ab6ef3037840393752d82fac01ea1eb4f97
Hello!
On Wed, May 31, 2017 at 01:54:05PM -0700, Piotr Sikora via nginx-devel wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1496263896 25200
> # Wed May 31 13:51:36 2017 -0700
> # Node ID e7219bf8bc3781d3912a951f09553bb2f0a53b70
> # Parent ab6ef3037840393752d82fac01ea1eb4f97
details: http://hg.nginx.org/nginx/rev/057ec63be834
branches:
changeset: 7017:057ec63be834
user: Piotr Sikora
date: Wed May 31 13:51:35 2017 -0700
description:
Headers filter: style.
Signed-off-by: Piotr Sikora
diffstat:
src/http/modules/ngx_http_headers_filter_module.c | 4 ++-
details: http://hg.nginx.org/nginx/rev/8ce1a34f160b
branches:
changeset: 7019:8ce1a34f160b
user: Maxim Dounin
date: Thu Jun 01 16:49:14 2017 +0300
description:
Style.
diffstat:
src/os/unix/ngx_udp_sendmsg_chain.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diffs
details: http://hg.nginx.org/nginx/rev/610a219b28f6
branches:
changeset: 7018:610a219b28f6
user: Piotr Sikora
date: Wed May 31 13:51:36 2017 -0700
description:
Upstream: style.
Signed-off-by: Piotr Sikora
diffstat:
src/http/ngx_http_upstream.c | 2 +-
1 files changed, 1 inserti
Hi, Maxim!
2017-05-30 18:01 GMT+05:00 Maxim Dounin :
>
> The maximum size of hash table as specified by the hinit->max_size
> field is indeed maximum size, and not the size of the hash table.
> Following code in the ngx_hash_init() will try hard to find to
> find out an optimal hash size for a giv
25 matches
Mail list logo