Hey Maxim,
> I have no strong objections, but the patch as you've submitted
> casts to "const char *", while just "char *" should be enough.
While cast to "char *" also works, I must admit that I'm confused as
to why do you prefer to cast to a type that "should be enough" instead
of a type that's
# HG changeset patch
# User Piotr Sikora
# Date 1476859139 25200
# Tue Oct 18 23:38:59 2016 -0700
# Node ID 1eec5355ef1e4a8b0aecebdec84c744734c0d36e
# Parent 8081e1f3ab8b9ccb4e2d7f9240cbfb8e404a3c95
HTTP: add support for "429 Too Many Requests" response (RFC6585).
This change adds reason ph
# HG changeset patch
# User Piotr Sikora
# Date 1476859304 25200
# Tue Oct 18 23:41:44 2016 -0700
# Node ID ae85978091f832d27d862e468ee5e4cbfb18da11
# Parent 8081e1f3ab8b9ccb4e2d7f9240cbfb8e404a3c95
SSL: decrease log level of SSL_R_NO_RENEGOTIATION to "info".
Previously, "no renegotiation"
# HG changeset patch
# User Piotr Sikora
# Date 1476859163 25200
# Tue Oct 18 23:39:23 2016 -0700
# Node ID cff70893f20b18623ed45c8406050bcf5db78a48
# Parent 1eec5355ef1e4a8b0aecebdec84c744734c0d36e
HTTP: change default response code when rate-limiting requests.
Previously, "503 Service Una
details: http://hg.nginx.org/nginx/rev/1bf4f21b1b72
branches:
changeset: 6776:1bf4f21b1b72
user: Vladimir Homutov
date: Tue Oct 18 16:33:38 2016 +0300
description:
Core: show file contents only once while dumping configuration.
Files are considered the same if the path used by nginx
details: http://hg.nginx.org/nginx/rev/563a1ee345a4
branches:
changeset: 6777:563a1ee345a4
user: Maxim Dounin
date: Wed Oct 19 18:36:50 2016 +0300
description:
SSL: compatibility with BoringSSL.
BoringSSL changed SSL_set_tlsext_host_name() to be a real function
with a (const char *)
Hello!
On Wed, Oct 19, 2016 at 12:51:30AM -0700, Piotr Sikora wrote:
> Hey Maxim,
>
> > I have no strong objections, but the patch as you've submitted
> > casts to "const char *", while just "char *" should be enough.
>
> While cast to "char *" also works, I must admit that I'm confused as
> to
