Re: forward bumped traffic to parent in plain form

Friday, April 3, 2026, 2:46:32 PM, you wrote:


> Friday, April 3, 2026, 2:20:17 PM, you wrote:


>> I've tried to call getSslContextStart() in startPeakAndSplice().

>> But the problem is:
>> getSslContextStart() return synchronously in most cases after calling getSslContextDone().

>> But in the case of #if USE_SSL_CRTD (my case) it return after sending request to CRTD without calling getSslContextDone().
>> getSslContextDone() will be called further in sslCrtdHandleReplyWrapper().

>> So we are back in startPeakAndSplice() without getSslContextDone() and connections are closed.

>> Is there a preferred way to solve this problem?

> Sorry. It's a normal. The problem is out here.


May be not.

I notice

26/04/03 16:54:33.312 kid1| 83,5| /client_side.cc(2993) startPeekAndSplice: Bumping on step2 done.
2026/04/03 16:54:33.312 kid1| 33,5| src/base/AsyncJob.cc(177) callEnd: Http1::Server status out: [ job4]     
-->2026/04/03 16:54:33.312 kid1| 33,5| src/base/AsyncCallQueue.cc(28) fire: leaving Server::doClientRead(conn12 
local=178.218.213.200:12345 remote=217.119.19.66:63055 FD 9 flags=1, data=0x2b2273397f18)
2026/04/03 16:54:33.341 kid1| 83,5| src/ssl/helper.cc(161) HandleGeneratorReply: to 0x2b2273397f18 in crtGenRq6569/1

and suggest that stack rewind out of Server::doClientRead() while waiting for HandleGeneratorReply. ?And connection somehow lost because next read was not triggered?
I'd like to wait inside startPeekAndSplice() for ?clientNegotiateSSL()? to finish.
But I don't want to introduce own "wait objects".

May be somebody can advice me.



-- 
Best regards,
Anthony