In D17136#379137, @rene wrote:

In D17136#379090, @bapt wrote:

I think this is a bad idea, openssl 1.1.0 and 1.1.1 are binary compatible

So we can also just remove openssl-devel completely? Or upgrade and rename it to openssl111 to preserve history.

Can I go ahead and change this throughout the ports tree?

SHLIB versions in base were changed to avoid conflicts in rS339741: Update SHLIB_VERSION_NUMBER following the OpenSSL shared library

From: brnrd@FreeBSD.org
To: umq@ueo.co.jp
CC: mat@FreeBSD.org
Subject: security/axTLSL: Removal of WITH_HTTP(S)_PORT

In D15412#347910, @mat wrote:

Did it have an effect before it was removed?

For security/axTLS it looks like it set the default https port. Probably I should include changes to that port here. Will contact maintainer.
For www/apache24 it has already been removed.

In D17668#378157, @ohauer wrote:

running the new release since yesterday on 12 hosts, all on 11-p4 and haven't seen any issues (the busiest hosts had round about 600.000 requests since the update).

OK, for me, but I will do a new test with the updated APR as soon my time permits the build/roll out

In D17688#378165, @ohauer wrote:

haven't looked deeper into the mysql issue, but perhaps it is similar to fix like the postfix ports.
Full conversation on the postfix-devel list https://marc.info/?t=151955691300001&r=1&w=2

Closed by rP482861

Works fine

Thanks for reporting. I have this in my local repo already, and am running Weechat 2.3 from my modified port.

Fix is needed for i386, not amd64

Abandoning this review. The main objective was to have an Apache that would work with OpenSSL 1.1 (and LibreSSL 2.7+) and support for TLSv1.3. Both these objectives have been/will be met by the 2.4 branch. As for the TLSv1.3 support, the discussions on apache httpd-dev mailing-list suggest that TLSv1.3 will land in a point-release of 2.4. Outlook on 2.6.x, for which 2.5 is the development branch, are that there won't be such a release soon.
2.4.x+TLSv1.3 branch (or git slave repo if you are so inclined)
Voting/discussion thread on http-dev mailing-list
Currently TLSv1.3 support is non-functional with released browsers, the browsers only support draft-13 and or 18. Testing requires BETA, nightly or canary builds. This will soon change.

This review was intended to be there to test TLSv1.3 with Apache.