Skip to main content
Deno 2 is finally here šŸŽ‰ļø
Learn more

deno_http_proxy_fns

NOTE: This is still fairly experimental.

A collection of functions for creating a HTTP proxy via a set of rules.

Accompanies http_fns, but could be used with any Deno server/router based on the standard Request/Response functions.

  • Configured via a single Manifest (JSON or TypeScript module).
  • Rules can filter based on URL pattern, method, and the ā€˜roleā€™ of the incoming request
  • Highly pluggable via functions, dynamic modules, or requests to external services
  • Pluggable ā€˜Role Providerā€™ determines the role of the incoming request
  • Pluggable Auditor chains

Docs and examples coming soon (hopefully).

Example

See the demo server.

Usage:

export OPENAI_API_KEY=...
deno task demo

(You can also declare env vars in a .env file)

Then hit http://localhost:8000/v1/models in your browser.

Manifest

The proxy is configured via a Manifest object, take a look at the example manifest in the demo, and the type declaration.

It is possible to declare the manifest entirely as a JSON file if you can rely on dynamic modules or remote services for all pluggable parts, otherwise use a regular typescript module.

Note: Deno Deploy doesnā€™t currently support dynamic module imports, so youā€™ll generally need to use a ts module for the manifest, and statically import role providers, auditor functions.