On Thu, 29 Apr 2021 at 22:36, Liwei wrote:
>
> On Thu, 29 Apr 2021 at 21:06, Rob Emery wrote:
> -- 8< Snip 8< -
> >
> > Yeah we actually already have that enabled in our access logs and we can
> > see that the clients in question are using TLS1.2 when
On Thu, 29 Apr 2021 at 21:06, Rob Emery wrote:
-- 8< Snip 8< -
>
> Yeah we actually already have that enabled in our access logs and we can
> see that the clients in question are using TLS1.2 when successful (i.e.
> on the next connection). However these connections that result in the
On 1 May 2017 at 19:17, Liwei wrote:
>
> Hi Nick, replies inline...
>
> On Mon, 1 May 2017 at 18:14 Nick Kew wrote:
>>
>> On Mon, 2017-05-01 at 15:08 +0800, Liwei wrote:
>> > Hi list,
>> > I'm seeing an unexpected behaviour when a 413 Reque
Hi Nick, replies inline...
On Mon, 1 May 2017 at 18:14 Nick Kew wrote:
> On Mon, 2017-05-01 at 15:08 +0800, Liwei wrote:
> > Hi list,
> > I'm seeing an unexpected behaviour when a 413 Request Entity Too
> > Large error occurs on a site proxied with
Too Large error was encountered
while trying to use an ErrorDocument to handle the request."
I do see the error page being requested on the proxied site by Apache,
but Apache does not show it.
Is this expected or unexpected behavior?
Warm regards,
Liwei
