Hey Maxim,
> Do we care? I think it's ok to assume HTTP by default, even if a
> client sent something different from what we've advertised.
I'm not sure about you, but I do. I don't see a point in trying to
process something that is known to fail down the line... Especially,
if it produces noise
Author: vbart
Date: 2013-04-03 14:13:35 + (Wed, 03 Apr 2013)
New Revision: 5167
URL: http://trac.nginx.org/nginx/changeset/5167/nginx
Log:
Limit req: rate should be non-zero.
Specifying zero rate caused division by zero when calculating delays.
Modified:
trunk/src/http/modules/ngx_http_l
Hello!
On Wed, Apr 03, 2013 at 12:09:25PM +0800, Weibin Yao wrote:
> Hi,
>
> Today In our test box I noticed that nginx sent bad response with 203
> response. You can reproduce the problem with the return directive:
>
> location / {
> return 203;
> }
>
> And the response looks like:
>
> H
Hello!
On Tue, Apr 02, 2013 at 06:06:02PM -0700, Piotr Sikora wrote:
> Hey,
> OpenSSL doesn't do anything to verify that "negotiated" protocol
> was actually advertised to the client, so we have to do it ourselves.
Do we care? I think it's ok to assume HTTP by default, even if a
client sent so
