Search Results for "router"

...We are committed to providing the simplest operation and meet most needs. Thanks to the advantages of Web GUI, you can not only use it on your local computer, but also easily deploy it on a router or NAS.

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.

chi is a lightweight, open source composable router for building Go HTTP services. It also helps in writing large REST API services, keeping them maintainable as the project evolves. Having been built on the latest context package, it can easily handle signaling, cancelation and request-scoped values across a handler chain. chi was built with the sole focus of providing an elegant and comfortable design for writing REST API servers.

jprq is an open-source tunneling tool for exposing local servers to the public internet. It is designed as a developer-friendly alternative to hosted tunneling platforms, making it useful for testing webhooks, APIs, websites, SSH, and other TCP-based services. The tool can publish a local port through a public address so external users or services can reach something running on a developer’s machine. It supports HTTP and general TCP use cases, which makes it more flexible than tools focused...

...We are committed to providing the simplest operation and meet most needs. Thanks to the advantages of Web GUI, you can not only use it on your local computer, but also easily deploy it on a router or NAS.

Package gorilla/mux implements a request router and dispatcher for matching incoming requests to their respective handler. The name mux stands for "HTTP request multiplexer". Like the standard http.ServeMux, mux.Router matches incoming requests against a list of registered routes and calls a handler for the route that matches the URL or other conditions. The main features are that it implements the http.Handler interface so it is compatible with the standard http.ServeMux, requests can be matched based on URL host, path, path prefix, schemes, header and query values, HTTP methods or using custom matchers, URL hosts, paths and query values can have variables with an optional regular expression. ...

...An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting. An Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic. An Ingress needs apiVersion, kind, metadata and spec fields. The name of an Ingress object must be a valid DNS subdomain name. For general information about working with config files, see deploying applications, configuring containers, managing resources.