📗
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

Overview

From a high level perspective, Janus will listen for HTTP traffic on its configured proxy port (8080 by default), recognize which upstream service is being requested, run the configured middlewares for that API, and forward the HTTP request upstream to your own API or service.

When a client makes a request to the proxy port, Janus will decide to which upstream service or API to route (or forward) the incoming request, depending on the API configuration in Janus, which is managed via the Admin API. You can configure APIs with various properties, but the three relevant ones for routing incoming traffic are hosts, uris, and methods.

If Janus cannot determine to which upstream API a given request should be routed, Janus will respond with:

HTTP/1.1 404 Not Found
Content-Type: application/json
Server: Janus/<x.x.x>

{
    "message": "no API found with those values"
}
PreviousTerminologyNextRouting capabilities

Last updated 4 years ago

Was this helpful?