Since this tag is only days away, the committers would really appreciate
any feedback from early adopters. I'm not certain on the status of the auth
hook fix, but believe it's certainly ready to have the tires kicked, so we
can avoid any quirks resulting from the TLS 1.3 efforts.
Please feel free
On Thu, Oct 4, 2018 at 7:20 PM William A Rowe Jr wrote:
>
> On Thu, Oct 4, 2018 at 12:09 PM Evgeny Kotkov
> wrote:
>>
>>
>> However, a more important question is whether there is an actual problem to
>> solve. I see that ap_http_header_filter() features a whitelist of headers
>> that are sent
On 07 Oct 2018, at 03:16, Daniel Ruggeri wrote:
> Actually, I'm glad you asked. I committed after 2.4.35 to T 2.4.36 soon
> after. I'm happy to do that ASAP if there are no objections.
>
> What say you, fellow devs? How about next week?
+1 and thank you. Would be good to see TLS 1.3 out the
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
