Search Results for "essential-static"

...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. ...

faasd is OpenFaaS reimagined but without the cost and complexity of Kubernetes. It runs on a single host with very modest requirements, making it fast and easy to manage. Under the hood it uses containers and Container Networking Interface (CNI) along with the same core OpenFaaS components from the main project. To deploy microservices and functions that you can update and monitor remotely. When you don't have the bandwidth to learn or manage Kubernetes. To deploy embedded apps in IoT and...

...Automatically install TLS certificates from https://letsencrypt.org. Proxy HTTP and WebSocket requests. Define virtual hosts with path level routing. Graceful shutdown. Limit request body. Serve static files. Log requests. Gzip response. Cross-origin Resource Sharing (CORS). Security, XSSProtection. ContentTypeNosniff. ContentSecurityPolicy. HTTP Strict Transport Security (HSTS). Add/Remove trailing slash from the URL with the option to redirect.

...There is no CONNECT involved nor needed because goflyway is designed mainly for those people who are behind a CONNECT-less HTTP proxy or want to accelerate connections through static CDNs. However pure HTTP requesting is definitely a waste of bandwidth if you already have a better network environment, so use -w to turn on WebSocket relay, or -K to turn on KCP relay if possible. In HTTP mode when the server received some data it can't just send them to the client directly because HTTP is not bi-directional, instead, the server must wait until the client requests them, which means these data will be stored in memory for some time.