v1.8.10

• fixes bugzilla PR60599, sending proper response for conditional requests
  answered by mod_cache. (orignal patch by Jeff Wheelhouse)

mod_h[ttp]2 v1.8.9

• rework of stream resource cleanup to avoid a crash in a close
  of a lingering connection. Prohibit special file bucket beaming for
  shared buckets. Files sent in stream output now use the stream pool
  as read buffer, reducing memory footprint of connections.
  (much help from Yann Ylavic)

mod_h[ttp]2 v1.8.8

• faster reaction to new requests/responses during output streaming

mod_h[ttp]2 v1.8.7

• fix for possible page fault when stream is resumed during session shutdown.
  (Patch by sidney-j-r-m, github)
• fix for h2 session ignoring new responses while already
  open streams continue to have data available.

mod_h[ttp]2 v1.8.6

• adding support for MergeTrailers directive.
• limiting DATA frame sizes by TLS record sizes in use on the
  connection. Flushing outgoing frames earlier.

mod_h[ttp]2 v1.8.5

• Removed log warning statements left over from debugging for 1.8.4

mod_h[ttp]2 v1.8.4

• Cleanup beamer registry on server reload, Fixes Apache bugzilla PR60510.
  Patch by Pavel Mateja [email protected]
• Fixes #126 e.g. beam bucket lifetime handling when data is sent
  over temporary pools.

mod_h[ttp]2 v1.8.3

• CVE-2016-8740: Mitigate DoS memory exhaustion via endless
  CONTINUATION frames. Reported by Naveen Tiwari [email protected] and
  CDF/SEFCOM at Arizona State University
• Removing some warning when streams are cleaned up that were never scheduled

mod_h[ttp]2 v1.8.2

• new directive 'H2EarlyHints' to enable sending of HTTP status 103 interim
  responses. Off by default since some browser still choke on them.
• mod_proxy_http2 will, when used on top of a HTTP/1.x connection, only
  forward 100 responses from the backend if the client expects them. All
  other responses in the 100 range are filtered.

mod_h[ttp]2 v1.8.0

• mod_http2: new directive 'H2PushResource' to enable early pushes before
  processing of the main request starts. Resources are announced to the
  client in Link headers on a 103 early hint response.
  All responses with status code <400 are inspected for Link header and
  trigger pushes accordingly. 304 still does prevent pushes.
  'H2PushResource' can mark resources as 'critical' which gives them higher
  priority than the main resource. This leads to preferred scheduling for
  processing and, when content is available, will send it first. 'critical'
  is also recognized on Link headers.
• mod_proxy_http2: uris in Link headers are now mapped back to a suitable
  local url when available. Relative uris with an absolute path are mapped
  as well. This makes reverse proxy mapping available for resources
  announced in this header.
  With 103 interim responses being forwarded to the main client connection,
  this effectively allows early pushing of resources by a reverse proxied
  backend server.
• mod_proxy_http2: adding support for 103 status code, as proposed by
  Kazuho Oku.