Skip to content

Releases: coupergateway/couper

v1.12.2

04 Dec 09:06
Compare
Choose a tag to compare

Note: The Couper project has been moved to a new home: https://github.com/coupergateway/couper !
The maintainer is still the same (@malud) and supported with ❤️ by Milecrew.
This affects the following locations which you have to update accordingly:

Dockerhub: coupergateway/couper and coupergateway/couper-oidc-gateway
VSCode-Extension: Couper Configuration (Marketplace / Open VSX)
Homebrew: brew tap coupergateway/couper and then brew install couper (formula)
Examples: https://github.com/coupergateway/couper-examples

  • Fixed
    • Reading the origin response-body even if there is no origin body or json_body variable reference; piping the response-body again to the client (#766)

v1.12.1

20 Mar 11:26
233f0d7
Compare
Choose a tag to compare

1.12.1

v1.12.0

30 Jan 15:52
Compare
Choose a tag to compare

1.12.0

  • Added

    • beta_job block to describe one or more job definitions for simple recurring http tasks (#610)
    • server_timing_header setting, that allows Couper to include an additional Server-Timing HTTP response header field detailing connection and transport relevant metrics for each backend request. (#657)
  • Changed

    • Use nested jwt_signing_profile block in oauth2 block for grant_type "urn:ietf:params:oauth:grant-type:jwt-bearer" in absence of assertion attribute (#619)
    • Improved the way an SPA bootstrap_file gets cached and served in combination with bootstrap_data (#656)
    • Harmonized and improved logged error information for references to undefined blocks (#651)
    • Unbeta permission features: (#673)
      • beta_required_permission attribute for api and endpoint blocks,
      • beta_granted_permissions and beta_required_permission request context variables,
      • beta_insufficient_permissions error type,
      • beta_permissions_claim, beta_permissions_map, beta_permissions_map_file, beta_roles_claim, beta_roles_map and beta_roles_map_file attributes for jwt block.
  • Fixed

VSCode-Extension

The vscode extension has been moved to our own publisher couper. The new extension can be found here:

v1.11.2

26 Jan 15:11
Compare
Choose a tag to compare

1.11.2

  • Fixed
    • Requests to wildcard (**) endpoints using backends with a wildcard path attribue, where the wildcard matches the empty string (regression; since v1.11.0) (#655)
    • [internal alloc] stop creating request context based jwt, oauth2 and saml (hcl) functions without related definitions (#666)
    • [internal alloc] reduced allocation amount while proxying requests (#666)
    • Removing websockets related headers while the proxy websockets option is false (or no block definition exist) (#666)

v1.11.1

05 Jan 13:10
Compare
Choose a tag to compare

1.11.1

v1.11.0

25 Nov 13:47
Compare
Choose a tag to compare

1.11.0

With this release Couper brings even more value when it comes to connecting services and security. We made mTLS configurable for both sides, the server side and the backend one. Couper is normally used behind an ingress but is now able to serve secured content and forces clients to present a valid certificate if configured. For the backend blocks Couper acts as client and is able to present a client certificate to the origin. This feature also allows to additionally configure a CA certificate per backend, unlike the ca_file option which configures a certificate for all outgoing connections.

To configure a Single Page Application for different environments, believe it or not, things could get complicated. Couper comes with a simple but powerful spa attribute to inject a custom JSON object into the bootstrap file via a defined placeholder while serving this to the client.

v1.10.1

19 Oct 08:56
Compare
Choose a tag to compare

1.10.1

v1.10.0

13 Sep 12:52
9833f65
Compare
Choose a tag to compare

1.10.0

Couper 1.10 is a feature release comprising new features for a more flexible and cleaner configuration. It also comes with some bug fixes and some smaller improvements. See below for a complete list of changes.

The new environment block along with its corresponding setting and the -e command line option allows for a cleaner and safer configuration if Couper is to be deployed in different environments. Read more about that feature in our example.

Labeled, reusable proxy blocks provide means for a leaner and less repetitive configuration.

In case a backend request requires authorization, the new beta_token_request block can request the required token and make the response available via the beta_token_response variable.

Finally, a stricter endpoint path validation for a clearer and more consistent path matching is now applied. Some characters or character sequences like ?, #, and /../ are no longer allowed; empty path parameters won't match anymore.

As always the Couper VSCode extension has been updated to support all new features.

We have launched our documentation website to find blocks and attributes more easily.

v1.9.2

28 Jun 12:29
Compare
Choose a tag to compare

1.9.2

v1.9.1

13 Jun 13:55
Compare
Choose a tag to compare

1.9.1

  • Fixed
    • missing environment key-error while using multiple configuration files (#522)