details: https://hg.nginx.org/nginx/rev/3db945fda515
branches:
changeset: 9164:3db945fda515
user: Vladimir Khomutov
date: Fri Sep 22 19:23:57 2023 +0400
description:
QUIC: handle callback errors in compat.
The error may be triggered in add_handhshake_data() by incorrect transport
pa
Hi,
> On 22 Sep 2023, at 19:58, Vladimir Homutov wrote:
>
> On Fri, Sep 22, 2023 at 07:30:50PM +0400, Roman Arutyunyan wrote:
>> Hi Vladimir,
>>
>> On Fri, Sep 22, 2023 at 03:44:08PM +0300, Vladimir Homutov via nginx-devel
>> wrote:
>>> # HG changeset patch
>>> # User Vladimir Khomutov
>>> #
Hello Andrey,
On Sun, Sep 24, 2023 at 02:30:14PM +0300, Andrey Kulikov wrote:
> Hello,
>
> Sometimes custom module developers need to iterate over configured
> location(s), configured in some or all server(s) blocks.
> For example, to perform post-initialization steps, defined by custom
> directi
Fyck off
On Mon, 25 Sep 2023 at 15:22, Roman Arutyunyan wrote:
> Hello Andrey,
>
> On Sun, Sep 24, 2023 at 02:30:14PM +0300, Andrey Kulikov wrote:
> > Hello,
> >
> > Sometimes custom module developers need to iterate over configured
> > location(s), configured in some or all server(s) blocks.
>
Hi Muhammad,
On Mon, Sep 25, 2023 at 12:01:11AM +0800, Muhammad Nuzaihan wrote:
> Hi,
>
> I would like to return an error message based on the *response* body.
>
> I know i can do it easily with *request* body (with "return
> NGX_HTTP_BAD_REQUEST") but my case i want to do it with *response*
> b
Hello!
On Mon, Aug 28, 2023 at 04:30:44PM +0400, Roman Arutyunyan wrote:
> # HG changeset patch
> # User Roman Arutyunyan
> # Date 1693218974 -14400
> # Mon Aug 28 14:36:14 2023 +0400
> # Node ID 42c3166b675a6a7624bdf3d78c0d4685ce8172e3
> # Parent fdad00808cb485ab83e919be59e9211ef06ac56a
>
