https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #8 from Eric Covener ---
(In reply to Yann Ylavic from comment #7)
> (In reply to Eric Covener from comment #2)
> >
> > Maybe a good sanity check would be to look
> > for mpm_state == AP_MPMQ_STARTING when
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #9 from Eric Covener ---
(In reply to Eric Covener from comment #8)
> (In reply to Yann Ylavic from comment #7)
> > (In reply to Eric Covener from comment #2)
> > >
> > > Maybe a good sanity check would be to
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #10 from Yann Ylavic ---
(In reply to Eric Covener from comment #9)
> > I assumed we wouldn't be able to enter the static functions that touch the
> > static variables, but I guess better safe than sorry.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60739
--- Comment #2 from David Favor ---
The following also works oddly.
SSLProtocol -all +TLSv1
This enables TLS 1.0 + 1.1 + 1.2 rather than just 1.0 as expected.
--
You are receiving this mail because:
You are the
https://bz.apache.org/bugzilla/show_bug.cgi?id=60739
--- Comment #1 from David Favor ---
Setting SSLProtocols to -all produces expected behavior, which is an error
about no protocols.
This suggests the problem relates to setting TLSv1.2, which incorrectly seems
to also
https://bz.apache.org/bugzilla/show_bug.cgi?id=60739
Bug ID: 60739
Summary: SSLProtocol settings seem to have no effect
Product: Apache httpd-2
Version: 2.4.25
Hardware: All
OS: Linux
Status: NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=60375
Joe Orton changed:
What|Removed |Added
Resolution|--- |FIXED
https://bz.apache.org/bugzilla/show_bug.cgi?id=60375
--- Comment #3 from Joe Orton ---
Oops. 2.4.x -> r1775832
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe,
https://bz.apache.org/bugzilla/show_bug.cgi?id=60088
Joe Orton changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #3 from Jeff Wheelhouse ---
"Did you take some explicit efforts to get a SIGHUP/WINCH sent during the load
of the module?"
No, unfortunately, it rears its ugly head all on its own.
"I am wondering if there
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #4 from Jacob P ---
Howdy,
On our customers servers, both backtraces involve a signal to gracefully
restart interrupting Apache while it is processing the configuration file in
various places.
We've been
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #5 from Jeff Wheelhouse ---
Jacob, is it alright if I contact you directly to discuss the issues you're
seeing? We're having two restart-related segfault problems, this is one and we
haven't reported the
https://bz.apache.org/bugzilla/show_bug.cgi?id=60487
--- Comment #7 from Yann Ylavic ---
(In reply to Eric Covener from comment #2)
>
> Maybe a good sanity check would be to look
> for mpm_state == AP_MPMQ_STARTING when retained == NULL and no-op'ing it
> altogether. An
13 matches
Mail list logo