Search Results for "interface"

go-mitmproxy is a Golang implementation of mitmproxy that supports man-in-the-middle attacks and parsing, monitoring, and tampering with HTTP/HTTPS traffic. Parses HTTP/HTTPS traffic and displays traffic details via a web interface. Supports a plugin mechanism for easily extending functionality. Various event hooks can be found in the examples directory. HTTPS certificate handling is compatible with mitmproxy and stored in the ~/.mitmproxy folder. If the root certificate is already trusted from the previous use of mitmproxy, go-mitmproxy can use it directly. ...

Plow is an HTTP(S) benchmarking tool, written in Golang. It uses excellent fast HTTP instead of Go's default net/http due to its lightning-fast performance. Plow runs at specified connections (option -c) concurrently and real-time records summary statistics, histogram of execution time and calculates percentiles to display on Web UI and terminal. It can run for a set duration( option -d), for a fixed number of requests(option -n), or until Ctrl-C is interrupted. The implementation of...

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 edge use-cases. To distribute applications to a customer or client. You have a cost sensitive project - run faasd on a 1GB VM for 5-10 USD / mo or on your Raspberry Pi. ...

...Supports both HTTP and HTTPS protocols, multi-user management, and cross-platform compatibility. Ideal replacement for traditional FTP servers, providing secure file sharing with intuitive web interface and enterprise-grade features for efficient file system management.

...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. Also, registered URLs can be built, or "reversed", which helps maintaining references to resources, Routes can be used as subrouters: nested routes are only tested if the parent route matches. ...

...HTTP client for manually creating/editing requests, and replay proxied requests. Intercept requests and responses for manual review (edit, send/receive, cancel) Scope support, to help keep work organized. Easy-to-use web-based admin interface. Project-based database storage, to help keep work organized.

...Although it's usually simpler to leave that to a reverse proxy (like nginx or Varnish), this package is useful when that's undesirable. Call GzipHandler with any handler (an object which implements the http.Handler interface), and it'll return a new handler which gzips the response.

Netgraph is a packet sniffer tool that captures all HTTP requests/responses, and displays them in a web page. You can run Netgraph in your Linux server without a desktop environment installed, and monitor HTTP requests/responses in your laptop's browser.