Log message:
Update apache24 to 2.4.23.

(NOTE: Versions 2.4.22 and 2.4.21 were not released.)

Changes from 2.4.20 are too many to write here, please refer CHANGES file.

And Apache 2.4.23 fixes CVE-2016-4979; X509 Client certificate based
authentication can be bypassed when HTTP/2 is used.

Log message:
Remove the stability entity, it has no meaning outside of an official context.

Log message:
Change the service_bundle name to "export" to reduce diffs between the
original manifest.xml file and the output from "svccfg export".

Log message:
Add comment:

When updating this package, make sure that no strings like
"PR 12345" are in the commit message. Upstream likes
to reference their own PRs this way, but this ends up
in NetBSD GNATS.

Log message:
Changes with Apache 2.4.20

  *) core: Do not read .htaccess if AllowOverride and AllowOverrideList
     are "None". PR 58528.

  *) mod_proxy_express: Fix possible use of DB handle after close.  PR 59230.

  *) core/util_script: relax alphanumeric filter of enviroment variable names
     on Windows to allow '(' and ')' for passing PROGRAMFILES(X86) et.al.
     unadulterated in 64 bit versions of Windows. PR 46751.

  *) mod_http2: incrementing keepalives on each request started so that logging
     %k gives increasing numbers per master http2 connection.
     New documented variables in env, usable in custom log formats: H2_PUSH,
     H2_PUSHED, H2_PUSHED_ON, H2_STREAM_ID and H2_STREAM_TAG.

  *) mod_http2: more efficient passing of response bodies with less contention
     and file bucket forwarding.

  *) mod_http2: fix for missing score board updates on request count, fix for
     memory leak on slave connection reuse.

  *) mod_http2: Fix build on Windows from dsp files.

Log message:
Bump PKGREVISION for security/openssl ABI bump.

Log message:
Detect pkgsrc lua. Fix PR pkg/50724

Log message:
Remove support for APACHE_CUSTOM_CFLAGS

This goes as far back as 2001 (mk.conf.example) but there should not be any
reason to explicitly set CFLAGS for specific packages. In practice this
even fixes support for global CFLAGS in www/apache{22,24}.

ok gdt@

Log message:
Changes with Apache 2.4.18

*) mod_ssl: for all ssl_engine_vars.c lookups, fall back to master connection
   if conn_rec itself holds no valid SSLConnRec*. Fixes 58666.

*) mod_http2: connection level window for flow control is set to protocol
   maximum of 2GB-1, preventing window exhaustion when sending data on many
   streams with higher cumulative window size.
   Reducing write frequency unless push promises need to be flushed.

*) mod_http2: required minimum version of libnghttp2 is 1.2.1

*) mod_proxy_fdpass: Fix AH01153 error when using the default configuration.
   In earlier version of httpd, you can explicitelly set the 'flusher' parameter
   to 'flush' as a workaround. (i.e. flusher=flush)
   Add documentation for the 'flusher' parameter when defining a proxy worker.

*) mod_ssl: For the "SSLStaplingReturnResponderErrors off" case, make sure
   to only staple responses with certificate status "good".

*) mod_http2: new directive 'H2PushPriority' to allow priority specifications
   on server pushed streams according to their content-type.

*) mod_http2: fixes crash on connection abort for a busy connection.
   fixes crash on a request that did not produce any response.

*) mod_http2: trailers are sent after reponse body if set in request_rec
   trailers_out before the end-of-request bucket is sent through the
   output filters.

*) mod_http2: incoming trailers (headers after request body) are properly
   forwarded to the processing engine.

*) mod_http2: new directive 'H2Push' to en-/disable HTTP/2 server
   pushes a server/virtual host. Pushes are initiated by the presence
   of 'Link:' headers with relation 'preload' on a response.

*) mod_http2: write performance of http2 improved for larger resources,
   especially static files.

*) core: if the first HTTP/1.1 request on a connection goes to a server that
   prefers different protocols, these protocols are announced in a Upgrade:
   header on the response, mentioning the preferred protocols.

*) mod_http2: new directives 'H2TLSWarmUpSize' and 'H2TLSCoolDownSecs'
   to control TLS record sizes during connection lifetime.

*) mod_http2: new directive 'H2ModernTLSOnly' to enforce security
   requirements of RFC 7540 on TLS connections.

*) core: add ap_get_protocol_upgrades() to retrieve the list of protocols
   that a client could possibly upgrade to. Use in first request on a
   connection to announce protocol choices.

*) mod_http2: reworked deallocation on connection shutdown and worker
   abort. Separate parent pool for all workers. worker threads are joined
   on planned worker shutdown.

*) mod_ssl: when receiving requests for other virtual hosts than the handshake
   server, the SSL parameters are checked for equality. With equal
   configuration, requests are passed for processing. Any change will trigger
   the old behaviour of "421 Misdirected Request".
   SSL now remembers the cipher suite that was used for the last handshake.
   This is compared against for any vhost/directory cipher specification.
   Detailed examination of renegotiation is only done when these do not
   match.
   Renegotiation is 403ed when a master connection is present. Exact reason
   is given additionally in a request note.

*) core: Fix scoreboard crash (SIGBUS) on hardware requiring strict 64bit
   alignment (SPARC64, PPC64).

*) mod_cache: Accept HT (Horizontal Tab) when parsing cache related header
   fields as described in RFC7230.

*) core/util_script: making REDIRECT_URL a full URL is now opt-in
   via new 'QualifyRedirectURL' directive.

*) core: Limit to ten the number of tolerated empty lines between request,
   and consume them before the pipelining check to avoid possible response
   delay when reading the next request without flushing.

*) mod_ssl: Extend expression parser registration to support ssl variables
   in any expression using mod_rewrite syntax "%{SSL:VARNAME}" or function
   syntax "ssl(VARNAME)".

Log message:
Remove mk/find-prefix.mk usage from the www category.

The find-prefix infrastructure was required in a pkgviews world where
packages installed from pkgsrc could have different installation
prefixes, and this was a way for a dependency prefix to be determined.

Now that pkgviews has been removed there is no longer any need for the
overhead of this infrastructure.  Instead we use BUILDLINK_PREFIX.pkg
for dependencies pulled in via buildlink, or LOCALBASE/PREFIX where the
dependency is coming from pkgsrc.

Provides a reasonable performance win due to the reduction of `pkg_info
-qp` calls, some of which were redundant anyway as they were duplicating
the same information provided by BUILDLINK_PREFIX.pkg.