📗
Janus Manual
  • Introduction
  • Installation
    • Docker
  • Quick Start
    • Authenticating
    • Add an endpoint
    • Modify (Update/Delete) an endpoint
    • Add Plugins
    • Authentication
    • Adding your API - File System
  • Clustering/HA
  • Proxy Reference
    • Terminology
    • Overview
    • Routing capabilities
    • Load Balacing
    • Request Host header
      • Using wildcard hostnames
      • The preserve_host property
    • Request URI
      • The strip_path property
      • The append_path property
    • Request HTTP method
    • Routing priorities
    • Conclusion
  • Plugins
    • Basic
    • Organization
    • Body Limit
    • Circuit Breaker
    • Compression
    • CORS
    • OAuth
    • Rate Limit
    • Request Transformer
    • Response Transformer
    • Retry
  • Auth
    • OAuth 2.0
  • Misc
    • Health Checks
    • Monitoring
    • Tracing
  • Known Issues
    • Stale HTTP Keep-Alive
  • Upgrade Notes
    • 2.x to 3.x
    • 3.6.x to 3.7.x
Powered by GitBook
On this page

Was this helpful?

  1. Proxy Reference

Terminology

API: This term refers to the API entity of Janus. You configure your APIs, that point to your own upstream services, through the Admin API.

Middleware: This refers to Janus "middleware", which are pieces of business logic that run in the proxying lifecycle. Middleware can be configured through the Admin API - either globally (all incoming traffic) or on a per-API basis.

Client: Refers to the downstream client making requests to Janus's proxy port.

Upstream service: Refers to your own API/service sitting behind Janus, to which client requests are forwarded.

PreviousProxy ReferenceNextOverview

Last updated 4 years ago

Was this helpful?