This version of the docs is a work in progress. If you don’t see what you are looking for check the legacy wiki. |
Enables users to add new headers and header values to a request and/or response.
Validates calls to an API by checking the URI format, enforcing Role-Based Access Control (RBAC), ensuring payload schema compliance, and much more.
Extracts a value from the request body and puts it in a request header.
Patches request/response bodies using methods native to the content type.
IN PROGRESS
Removes the Content-Type
header when no content body is present.
Enables users to add support for Cross-Origin Resource Sharing requests.
IN PROGRESS
IN PROGRESS
IN PROGRESS
IN PROGRESS
IN PROGRESS
Conditionally removes headers from a request and/or response.
IN PROGRESS
IN PROGRESS
Logs a descriptive event for each API request so that usage can be audited.
Populates a request header with the client’s IP address.
Verifies that the request URI has been properly converted from an IRI.
Provides a mechanism for authenticating and enriching requests with data from an OpenStack Keystone v2 Identity service.
Authorizes requests based on data about the user making the request.
IN PROGRESS
Merges multiple header lines with the same name into a single header line with multiple comma-separated values.
Validates requests against a configured OpenAPI Document.
Authenticates, authorizes, and enriches requests using data from an OpenStack Identity v3 service.
Limits the number of requests allowed through Repose to the origin service.
Validates calls to an API by checking the requested URI against a series Regular Expressions to enforce Role-Based Access Control (RBAC).
Enables users to write custom filters for Repose using a variety of scripting languages.
Validates calls to an API by checking the URI format and HTTP method and enforcing Role-Based Access Control (RBAC) using a simple Domain Specific Language (DSL).
IN PROGRESS
Splits header lines with multiple values into multiple header lines each with a single value.
Winnows away the tenants that are not relevant to the current request.
IN PROGRESS
Normalizes the URI of HTTP messages.
IN PROGRESS
IN PROGRESS
IN PROGRESS
Authorizes users with permissions from a Valkyrie service, and normalizes request and/or response data given those permissions.
IN PROGRESS