gateway

The HTTP entry point to a reva deployment: one address that accepts every request and forwards it to the service that declared the route it matches.

Package
github.com/cs3org/reva/v3/internal/http/services/gateway
Source
internal/http/services/gateway · Go reference

Enable it

Add this table to the revad configuration file:

[http.services.gateway]
# settings below

Overview

Package gateway is the HTTP entry point to a reva deployment: one address that accepts every request and forwards it to the service that declared the route it matches.

It keeps no route list of its own. Every HTTP service advertises the routes it declared in the service registry, and the gateway mirrors them into a router of the same kind the services themselves use, so a request is matched here exactly as it would be at the service. Adding an endpoint to a service, or a whole service to the deployment, needs no change here and none in whatever sits in front.

Configuration

KeyTypeDefaultDescription
refresh_intervalstring"10s"RefreshInterval is how often the mirrored routes are rebuilt from the registry, picking up services that appeared or went away. source
services[]string-Services, when set, limits the gateway to these service names. Empty means every HTTP service in the registry. source
exclude[]string-Exclude drops these service names. Endpoints not meant for the outside (pprof, prometheus) belong here. source
flush_intervalstring"-1"FlushInterval is how often a streamed response is flushed to the client. Negative flushes immediately, which is what a long-lived response needs. source