Hello!
On Thu, Sep 29, 2022 at 05:53:52PM +0400, Sergey Kandaurov wrote:
>
> > On 28 Sep 2022, at 01:04, Maxim Dounin wrote:
> >
> > Hello!
> >
> > On Tue, Sep 27, 2022 at 04:05:54PM +0400, Sergey Kandaurov wrote:
> >
> >>> On 27 Sep 2022, at 14:11, João Sousa Andrade
> >>> wrote:
> >>>
>
> On 28 Sep 2022, at 01:04, Maxim Dounin wrote:
>
> Hello!
>
> On Tue, Sep 27, 2022 at 04:05:54PM +0400, Sergey Kandaurov wrote:
>
>>> On 27 Sep 2022, at 14:11, João Sousa Andrade
>>> wrote:
>>>
>>> Thank you for the clarification Sergey.
>>>
>>> We have been running http3 in production f
Hello!
On Tue, Sep 27, 2022 at 04:05:54PM +0400, Sergey Kandaurov wrote:
> > On 27 Sep 2022, at 14:11, João Sousa Andrade
> > wrote:
> >
> > Thank you for the clarification Sergey.
> >
> > We have been running http3 in production for the past couple of weeks.
> > There's something we have n
> On 27 Sep 2022, at 14:11, João Sousa Andrade wrote:
>
> Thank you for the clarification Sergey.
>
> We have been running http3 in production for the past couple of weeks.
> There's something we have noticed which I'm not entirely sure as to what is
> causing it.
>
> We have been getting l
Thank you for the clarification Sergey.
We have been running http3 in production for the past couple of weeks. There's
something we have noticed which I'm not entirely sure as to what is causing it.
We have been getting lots of errors of the form: "[error] 34#34: *338736 quic
no available clie
> On 8 Sep 2022, at 14:27, João Sousa Andrade via nginx wrote:
>
> Hello everyone,
>
> My team is currently considering using nginx-quic in a production-like
> environment after running it and benchmarking it in our test env.
>
> Reading "The code is currently at a beta level of quality and s