# HG changeset patch
# User Xiaochen Wang
# Date 1382350832 -28800
# Node ID b61b9d7d665fffd49fb6711db4d018a6aeb26222
# Parent fcecb9c6a0573f2edd48ff87cef69bd7e7523729
round robin: optimize loop in ngx_http_upstream_init_round_robin()
It is a trivial patch to move continue statement from inner
Configure:
./configure --with-http_spdy_module --with-http_stub_status_module
--prefix=$(pwd)/../nginx --with-cc-opt=-O0
Reproduce:
1. use nginx(spdy/2) to build static file server
2. request large static file(16MB file, 10 streams in one session)
$ spdycat --no-tls -2 -m 10 http://ip:spdy_por
See the patch as following:
# HG changeset patch
# User Xiaochen Wang
# Date 1386913049 -28800
# Node ID 9af659c4cf71e668183d6a3e2abe1effb89ced22
# Parent f6258a7092e4edc24ee084944eda8a460c549970
SPDY: fix bug that "tcp_nopush off" doesnt work
ngx_http_update_location_co
# HG changeset patch
# User Xiaochen Wang
# Date 1392123256 -28800
# Node ID d8d499624b0941a989e43538ac33aead31d55efb
# Parent eeb3c27191471471ff8c3853d847399264498463
SPDY: fixed parsing of http version
There is an error while parsing multi-digit minor version numbers (e.g.
"HTTP
with wrong
sc->length, which broke spdy stream.
# HG changeset patch
# User Xiaochen Wang
# Date 1395807655 -28800
# Node ID c18a0115c6027ad0ad475061d2984d90544d8449
# Parent bd91f286ee0ade98e9c0f8f55bfef54a122adaf2
SPDY: fixed handling of sc->length in ngx_http_spdy_state_read_data()
d
hi,
On Wed, Mar 26, 2014 at 3:02 PM, Valentin V. Bartenev wrote:
> On Wednesday 26 March 2014 12:30:11 Xiaochen Wang wrote:
> > In our production, sometimes, the disk was full. In which case, the
> requests
> > after the POST request were handled wrongly in one spdy connectio
hi
On Thu, Mar 27, 2014 at 1:01 AM, Valentin V. Bartenev wrote:
> On Wednesday 26 March 2014 12:30:11 Xiaochen Wang wrote:
> > In our production, sometimes, the disk was full. In which case, the
> requests
> > after the POST request were handled wrongly in one spdy connectio
On Wed, Nov 5, 2014 at 1:44 PM, Steven Lu wrote:
> Hello
>
> I am looking for some test tools, test cases, test dataset for nginx to test
> if my changes introduce any regression issues. But I did not find them in
> the nginx community. Can anyone point me where I can find them if there are?
You
tart nginx listening on port 8080 or other ports.
> 2. Any test tools for performance tests?
>
>
>
> On 11/5/14, 2:39 PM, "Xiaochen Wang" wrote:
>
>>On Wed, Nov 5, 2014 at 1:44 PM, Steven Lu wrote:
>>> Hello
>>>
>>> I am looking for some
] 17320#0: signal process started (reopen)
2014/12/18 11:47:44 [notice] 17346#0: signal process started (reload)
# HG changeset patch
# User Xiaochen Wang
# Date 1418872566 -28800
# Node ID 179a8ce4f68f96c316e4daec3fa677cd7d4e0126
# Parent 99751fe3bc3b285801b434f7f707d87fa42b093e
Core: added signal
On Sat, Dec 20, 2014 at 1:27 AM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Dec 18, 2014 at 12:05:01PM +0800, Xiaochen Wang wrote:
>
>> It is useful to know which signal was sent to nginx master when we analyzed
>> error.log. If error_log level is warn/error/crit/alert/eme
# HG changeset patch
# User Xiaochen Wang
# Date 1426427181 -28800
# Node ID ec3b9c4277e33bfc9b25bbee67b74d5ee528366a
# Parent 79b473d5381d85f79ab71b7aa85ecf9be1caf9fb
SPDY: fixed format specifiers in logging.
diff -r 79b473d5381d -r ec3b9c4277e3 src/http/ngx_http_spdy.c
--- a/src/http
12 matches
Mail list logo