Search Results for "essential-static"

Reproxy is a simple edge HTTP(s) server / reverse proxy supporting various providers (docker, static, file, consul catalog). One or more providers supply information about the requested server, requested URL, destination URL, and health check URL. It is distributed as a single binary or as a docker container. Both HTTP and HTTPS are supported. For HTTPS, static certificates can be used as well as automated ACME (Let’s Encrypt) certificates.

...Everything you would require in your infrastructure, from TLS certificate renewals and OCSP stapling, to reverse proxying and ingress, Caddy simplifies it all. Its modular architecture lets you do more with just a single static binary that compiles for any platform. Caddy is the only web server that uses HTTPS automatically and by default. It automatically renews TLS certificates, staples OCSP responses and more. Though used mostly as an HTTPS server, Caddy can be used to run Go applications, offering automated documentation, graceful on-line config changes via API and more to these apps. ...

Skipper is an HTTP router and reverse proxy for service composition. It’s designed to handle large amounts of dynamically configured HTTP route definitions (>800000 routes) with detailed lookup conditions, and flexible augmentation of the request flow with filters. It can be used out of the box or extended with custom lookup, filter logic and configuration sources. Skipper identifies routes based on the requests’ properties, such as path, method, host and headers using the predicates. It...

A reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. If you are running a version older than v6.0.0 we strongly recommend you please update to the current version. After returning from the authentication provider, the OAuth tokens are stored in the configured session store (cookie, redis, ...) and a cookie is set.

...Each inbound WebSocket connection runs your program in a dedicated process. Connections are isolated by process. Available for Linux, OSX, Windows, FreeBSD, OpenBSD and Solaris. Serves your static HTML, JavaScript, etc. Route different URLs to different programs. Dynamic generate content over HTTP too. Out-of-the-box support for serving content using HTTPS and WSS. Restrict which pages can make WebSocket connections. Interact with your WebSocket programs before you've built your frontend.