Bosca / Gateway

Routes

The path decides where it goes

A route matches a request — by path, and by host if you want — and hands it to an upstream. The matching rules are few, and their precedence is predictable.

Patterns

Three pattern shapes, two host rules

Paths match by prefix, by a single segment, or exactly. Hosts match literally or by a leading wildcard — and when several routes could match, the more specific one wins.

  • Path shapes — /reports/** for a whole subtree, /reports/* for one segment, or an exact path like /health.
  • Hosts — a literal like api.bosca.io, a wildcard like *.bosca.io, or nothing to match any host. Literal beats wildcard beats any.
  • Ties are yours to break — a sort order decides between equally-specific routes; lower wins.
  • Strip the prefix — optionally drop the matched prefix before forwarding, so /warehouse/v1/query arrives upstream as /v1/query.
routes
/warehouse/**→ warehouse · strip prefix
/dashboards/**→ dashboards
/health→ status · exact
*.reports.example.comhost wildcard

Presets

Picky services, preconfigured

Some services are particular about how they're proxied. A preset overlays the right field values onto the route form — and leaves everything you've already set alone.

  • The data warehouse — sets the path pattern and prefix stripping, and spells out what the warehouse needs configured to accept a proxy in front of it.
  • Raw pass-through — no prefix stripping, no injected headers; the gateway forwards the request as-is.
  • Custom — the default: start from a blank route and set every field yourself.
preset · data warehouse
Path pattern/warehouse/**
Strip prefixon
Hintcoordinator settings to check

Keep exploring

More on Gateway

Gateway overview

Your services, behind one authenticated front door.

Upstreams

Register a service, watch its health, tune its connection.

Access

Sign-in methods, group rules, and forwarded identity.