Headers will no longer be split unnecessarily at the boundaries of Repose. If you were counting on this behavior, or for a list of headers that were being split, see Pre 9.0 Header Splitting.

Headers with an empty value will no longer be automatically removed from requests or responses. If you were counting on this behavior, the Scripting Filter can be used. The scripting filter configuration may look like the following:

<?xml version="1.0" encoding="UTF-8"?>
<scripting xmlns="http://docs.openrepose.org/repose/scripting/v1.0"
         language="groovy">
  request.headerNames.each { headerName ->
      if (!request.getHeader(headerName)) {
          request.removeHeader(headerName)
      }
  }
  filterChain.doFilter(request, response)
  response.headerNames.each { headerName ->
      if (!response.getHeader(headerName)) {
          response.removeHeader(headerName)
      }
  }
</scripting>

The response status line reason phrase from the origin service will now be forwarded from the origin service. If you need Repose to normalize the reason phrase, see the Reason Phrase Normalization recipe.

Requests can now contain headers with empty values. For example, if Repose receives a request with the header line `My-Header: `, that header line will now be forwarded to the origin service.

Some core classes have been renamed. If you need to customize the logging behavior for the loggers used by these classes, or if you rely on these classes directly, use the following mapping to update to the new class names:

The Response Messaging Service has been removed. If you were counting on this behavior, the Scripting Filter can be used. The scripting filter configuration may look like the following:

<?xml version="1.0" encoding="UTF-8"?>

<scripting xmlns="http://docs.openrepose.org/repose/scripting/v1.0"
           language="groovy"><![CDATA[
    import groovy.xml.MarkupBuilder

    //Continue the filter chain
    filterChain.doFilter(request, response)

    //Check to see if we should monkey with the response because we have xml and a 2xx
    if((response.contentType ==~ /.*(xml|XML).*/) && (response.status >= 400) && (response.status < 600)) {

        //Uncommit the response just in case
        response.uncommit()

        //Clear the current response body
        response.resetBuffer()

        //Write the new body
        def xml = new MarkupBuilder(response.getWriter())
        xml.error() {
            status(response.getStatus())
            message(response.getReason())
        }
    }
]]></scripting>

The Filter Chain now determines whether or not a filter should run based on the current state of the request rather than the state of the request when it was initially received. If you are applying a condition to filter activation (e.g., using the uri-regex attribute) and you modify some part of the request (e.g., the URL) in one of your filters, you may be impacted by this change. For more details, see filter activation determination.

Support for multi-cluster deployments has been removed.

The via attribute was removed from the container configuration. It has been replaced with the via-header element. To replicate the previous behavior set the value that was previously in the via attribute in the request-prefix and response-prefix attributes of the new element.

The soLingerTime attribute was removed from the container configuration. The underlying Jetty server no longer respects this value and therefore Repose will no longer expose it. To replicate the previous behavior you need to configure it in the operating system.

Support for installing Repose into an existing container has been dropped. For help moving to another deployment see Valve Installation and Quick Start with Docker.

The package for valve installation has changed from repose-valve to repose.

The Scripting Filter has been moved from the repose-experimental-filter-bundle to the repose-filter-bundle.

If setting the chunked-encoding attribute, it will no longer be set in HTTP Client Service configuration but instead will be set in the System Model configuration.

The http.connection.max-status-line-garbage configuration attribute has been removed from the schema, and thus must be removed from configuration instances if present. This attribute has never affected the processing performed by Repose, and so it should be safe to remove in all cases.

Consult with identity for where these filters now live.

All matching targets will now be processed, previously only the first target that matched would be evaluated.

All capture groups in the URL regex will now add their captured values to the desired header.

Removed deprecated caching attributes:

Cache timeouts are now defined in seconds rather than milliseconds.

The uri-tenant-quality attribute was removed; the validated-tenant-quality should be used in its place.

Support for extracting required tenant ID(s) from the URI was removed from the Keystone v2 Authorization Filter and Keystone v2 Filter configuration. To continue validating tenant ID(s) from the URI, follow these steps: