On Fri, Jul 2, 2021 at 2:09 PM RONDEC JUNE RUBIO
wrote:
>
> I have not tried to repro the issue with higher version. Is it known issue?
Not to me (doesn't ring a bell). But I'm not very inclined to
investigate if it's already fixed..
Regards;
Yann.
--
I have not tried to repro the issue with higher version. Is it known issue?
On Fri, Jul 2, 2021, 7:44 PM Yann Ylavic, wrote:
> Hi,
>
> On Fri, Jul 2, 2021 at 8:04 AM RONDEC JUNE RUBIO
> wrote:
> >
> > I've been investigating this issue with httpd corrupted memory and
> throwing SIGILL. I can pi
Hi,
On Fri, Jul 2, 2021 at 8:04 AM RONDEC JUNE RUBIO
wrote:
>
> I've been investigating this issue with httpd corrupted memory and throwing
> SIGILL. I can pinpoint what makes the memory corrupted. Is this known issue
> guys could someone shed some light.
>
> callstack :
> Core was generated by
When checking for https HSTS compliance on htstpreload.org I get a warning
> We cannot connect to https://example.net using TLS ("Get https://example.net:
> http: server gave HTTP response to HTTPS client").
And I do not understand how this can be. The page in questions loads as https
with a v
