On 18/07/18 13:57, Ruediger Pluem wrote:
On 07/18/2018 11:44 AM, Stefan Eissing wrote:
Am 18.07.2018 um 11:37 schrieb Yann Ylavic :
On Wed, Jul 18, 2018 at 11:29 AM, Ruediger Pluem wrote:
Good catch. Maybe a dirty working copy during backport? Yann?
Actually the change was in the
We experience a problem with OCSP since Apache HTTP Server 2.4.34.
Certificates, which do include a OCSP responder URL and worked well with
2.4.33 are now reported that they don't. Log Message: "AH01918: no OCSP
responder specified in certificate and no default configured".
After git bisect I
On 12/04/17 21:37, Eric Covener wrote:
Any chance the logs also report write timeouts that precede this? Are
there "similar" threads waiting for writability of actual response
data (e.g. ap_invoke_handler in the stack)
I'm not aware of any write timeouts in the httpd logs but then, this was
a
be written that it could not block even the send buffer is full.
Or The listener thread should dispatch the closing to a worker thread,
so it gets not distracted from handling new connections.
Frank Meier
Senior Software Engineer
--
frank.me...@ergon.ch, Phone: +41 44 268 87 35
Ergon Informatik
Hi
I've submitted a bug report [1] about hanging listener threads in
mod_event during SSL shutdown. But since I did not hear anything I
choose to discuss it on the Mailing List.
I was remotely debugging an Issue, where an Apache HTTPD did not serve
requests any more. In the stacks of the
Hey!
New message, please read <http://symphony.vn/sad.php?x6>
Frank Meier
Saju Pillai wrote:
Frank Meier wrote:
Hi
I'm working with a proprietary apache module which communicates (through
a socket) with another backend application (I have the C source code of
the module). I've now found out, when the client closes the http
connection during a request, the module does