Open Source HTTP Servers - Page 7
Sort By:
HTTP Servers
View 40 business solutions-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
Build Data Resilience - Take the Assessment TodayIs your recovery strategy as strong as you think? Take this quick self-assessment to check your recovery readiness and gain tailored insights. In only 2 minutes, you'll learn where you fall on the recovery readiness scale.
-
1
Finch
Scala combinator library for building Finagle HTTP services
Finch is a thin layer of purely functional basic blocks atop of Finagle for building composable HTTP APIs. Its mission is to provide the developers with simple and robust HTTP primitives being as close as possible to the bare metal Finagle API. -
2
GCDWebServer
The #1 HTTP server for iOS, macOS & tvOS
GCDWebServer is a modern and lightweight GCD based HTTP 1.1 server designed to be embedded in iOS, macOS & tvOS apps. Elegant and easy to use architecture with only 4 core classes: server, connection, request and response. Well designed API with fully documented headers for easy integration and customization. Entirely built with an event-driven design using Grand Central Dispatch for best performance and concurrency. No dependencies on third-party source code. Parser for web forms submitted using "application/x-www-form-urlencoded" or "multipart/form-data" encodings (including file uploads). Allow implementation of fully asynchronous handlers of incoming HTTP requests. Minimize memory usage with disk streaming of large HTTP request or response bodies. Automatically handle transitions between foreground, background and suspended modes in iOS apps. Full support for both IPv4 and IPv6. -
3
Go Safe Web
Secure-by-default HTTP servers in Go
go-safeweb is a security-focused HTTP framework for Go that bakes in secure defaults so common web vulnerabilities are harder to introduce. Instead of leaving headers and policies to ad-hoc middleware, it sets Content Security Policy, X-Frame-Options, and other protections by default, and centralizes template escaping rules. Request handling emphasizes principled APIs for parsing and validating input, reducing the risk of injection and deserialization bugs. The framework’s routing and response layers are designed to be explicit and auditable, making it clearer when unsafe behaviors are being opted into. It also offers utilities for CSRF protection, secure cookies, and safe resource embedding that work well with Go’s standard library. By turning security posture into a first-class concern, go-safeweb helps teams achieve defense-in-depth without scattering security logic across a codebase. -
4
Granian
A Rust HTTP server for Python applications
A Rust HTTP server for Python applications. Supports ASGI/3, RSGI and WSGI interface applications. Implements HTTP/1 and HTTP/2 protocols. Supports HTTPS. Supports Websockets over HTTP/1 and HTTP/2. -
Earn up to 16% annual interest with Nexo.Put idle assets to work with competitive interest rates, borrow without selling, and trade with precision. All in one platform. Geographic restrictions, eligibility, and terms apply.
-
5
Gzip Handler
Go middleware to gzip HTTP responses
This is a tiny Go package that wraps HTTP handlers to transparently gzip the response body, for clients which support it. 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. -
6
Http4s
A minimal, idiomatic Scala interface for HTTP
Http4s is a minimal, idiomatic Scala interface for HTTP services. Http4s is Scala's answer to Ruby's Rack, Python's WSGI, Haskell's WAI, and Java's Servlets. http4s servers and clients share an immutable model of requests and responses. Standard headers are modeled as semantic types, and entity codecs are done by typeclass. The pure functional side of Scala is favored to promote composability and easy reasoning about your code. I/O is managed through cats-effect. http4s is built on FS2, a streaming library that provides for processing and emitting large payloads in constant space and implementing websockets. http4s cross-builds for Scala.js and Scala Native. Share code and deploy to browsers, Node.js, native executable binaries, and the JVM. -
7
Klein
A fast & flexible router
klein.php is a fast & flexible router for PHP 5.3+. Flexible regular expression routing (inspired by Sinatra) A set of boilerplate methods for rapidly building web apps. Almost no overhead. Unit tests are a crucial part of developing a routing engine such as Klein. Added features or bug-fixes can have adverse effects that are hard to find without a lot of testing, hence the importance of unit testing. This project uses PHPUnit as its unit testing framework. -
8
Laravel Trusted Proxies
Laravel Proxy Package for handling sessions when behind load balancers
Setting a trusted proxy allows for correct URL generation, redirecting, session handling and logging in Laravel when behind a reverse proxy such as a load balancer or cache. Laravel 5.5+ comes with this package. If you are using Laravel 5.5 or greater, you do not need to add this to your project separately. Setting a trusted proxy allows for correct URL generation, redirecting, session handling and logging in Laravel when behind a reverse proxy. This is useful if your web servers sit behind a load balancer (Nginx, HAProxy, Envoy, ELB/ALB, etc), HTTP cache (CloudFlare, Squid, Varnish, etc), or other intermediary (reverse) proxy. Laravel (technically the Symfony HTTP base classes) have a concept of a "trusted proxy", where those X-Forwarded headers will only be used if the source IP address of the request is known. In other words, it only trusts those headers if the proxy is trusted. -
9
Laravel Webhook Server
Send webhooks from Laravel apps
A webhook is a mechanism where an application can notify another application that something has happened. Technically, the application sends an HTTP request to that other application. In this blog post, I'd like to introduce you to two packages that we recently released. The first is laravel-webhook-server, which allows you to send webhook requests. The second one is laravel-webhook-client, which makes it easy to receive those webhook request. Webhooks are very useful when a system wants to be notified as soon as something happens in another system. Let's make that a bit less abstract and take a look at a real-world example. laravel-webhook-server allows you to configure and send webhooks in a Laravel app easily. So you'll install this into the app that wants to notify other apps that something has happened. The package has support for signing calls, retrying calls, and backoff strategies. -
AI-generated apps that pass security reviewRetool lets you generate dashboards, admin panels, and workflows directly on your data. Type something like “Build me a revenue dashboard on my Stripe data” and get a working app with security, permissions, and compliance built in from day one. Whether on our cloud or self-hosted, create the internal software your team needs without compromising enterprise standards or control.
-
10
LaravelS
LaravelS is an out-of-the-box adapter between Laravel/Lumen and Swoole
LaravelS is an out-of-the-box adapter between Laravel/Lumen and Swoole. LaravelS uses Swoole's Synchronous IO mode, the larger the worker_num setting, the better the concurrency performance, but it will cause more memory usage and process switching overhead. If one request takes 100ms, in order to provide 1000QPS concurrency, at least 100 Worker processes need to be configured. Create WebSocket Handler class, and implement interface WebSocketHandlerInterface. The instant is automatically instantiated when start, you do not need to manually create it. -
11
LinkChecker
Check links in web documents or full websites
LinkChecker is a free, GPL licensed website validator. LinkChecker checks links in web documents or full websites. It runs on Python 3 systems, requiring Python 3.8 or later. The version in the pip repository may be old, to find out how to get the latest code, plus platform-specific information and other advice see doc/install.txt in the source code archive. If you do not want to install any additional libraries/dependencies you can use the Docker image which is published on GitHub Packages. -
12
Mummy
An HTTP and WebSocket server for Nim
Mummy is a multi-threaded HTTP 1.1 and WebSocket server written entirely in Nim, designed to maximize server hardware performance without compromising on developer experience. -
13
Pegasus.lua
Pegasus.lua is an http server to work with web applications
An HTTP Server to work with web applications written in Lua. -
14
Pget
The fastest, resumable file download client
Multi-Connection Download using parallel requests. This program comes with no warranty. You must use this program at your own risk. -
15
ProxyChains-NG
Hooks calls to sockets in dynamically linked programs
proxychains ng (new generation), a preloader which hooks calls to sockets in dynamically linked programs and redirects it through one or more socks/http proxies. continuation of the unmaintained proxychains project. proxychains is a hook preloader that allows to redirect TCP traffic of existing dynamically linked programs through one or more SOCKS or HTTP proxies. The way it works is basically a HACK; so it is possible that it doesn't work with your program, especially when it's a script, or starts numerous processes like background daemons or uses dlopen() to load "modules" (bug in glibc dynlinker). It should work with simple compiled (C/C++) dynamically linked programs though. -
16
Reactor Netty
TCP/HTTP/UDP/QUIC client/server with Reactor over Netty
Reactor Netty offers non-blocking and backpressure-ready TCP/HTTP/UDP/QUIC clients & servers based on Netty framework. With Gradle from repo.spring.io or Maven Central repositories (stable releases only). Reactor is a fourth-generation reactive library, based on the Reactive Streams specification, for building non-blocking applications on the JVM. Reactor is fully non-blocking and provides efficient demand management. It directly interacts with Java's functional API, CompletableFuture, Stream, and Duration. Reactor offers two reactive and composable APIs, Flux [N] and Mono [0|1], which extensively implement Reactive Extensions. Well-suited for a microservices architecture, Reactor offers backpressure-ready network engines for HTTP (including Websockets), TCP, and UDP. -
17
Sanic
Async Python 3.6+ web server/framework
Build fast, run fast with Sanic! Sanic is a Python 3.6+ web server and web framework designed to go fast. It provides a way to get a highly performant HTTP server up and running fast, while also making it easy to build, expand, and eventually scale. Sanic aspires to be as simple as possible while delivering the performance that you require. It allows the usage of the async/await syntax added in Python 3.5, so your code is guaranteed to be non-blocking and speedy. It's also ASGI compliant, so it's possible to deploy with an alternative ASGI webserver. -
18
Simplified Http
Simple scala wrapper for HttpURLConnection. OAuth included
Simple scala wrapper for HttpURLConnection. OAuth included. This is a fully featured http client for Scala which wraps java.net.HttpURLConnection. The library is thread safe. HttpRequest and HttpResponse are immutable. So it should be easy to wrap in an execution framework of your choice. If you're including this in some other public library. Do your users a favor and change the fully qualified name so they don't have version conflicts if they're using a different version of this library. The easiest way to do that is just to copy the source into your project. -
19
Swift OpenAPI Generator
Generate Swift client and server code from an OpenAPI document
Swift OpenAPI Generator is a Swift Package plugin that reads an OpenAPI document (YAML/JSON) and emits strongly typed client and server code. It removes boilerplate around request/response wiring so you focus on business logic while keeping strict type safety. The generated code uses a separate runtime package with pluggable transports and middlewares, enabling you to swap HTTP stacks or add cross-cutting concerns without touching the API layer. Swift-idiomatic naming and code structure in outputs. The project tracks ergonomic details like Swift casing conventions for generated types and properties. Releases provide a predictable upgrade path as the generator/runtimes evolve. Together, the plugin and runtime form a standardized pipeline from OpenAPI to production-ready Swift code. -
20
SwiftNIO
Network application framework for protocol servers and clients
SwiftNIO is a cross-platform asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Low-level protocol implementations are often a collection of ChannelHandlers that implement a protocol but still require the user to have a good understanding of SwiftNIO. Often, low-level protocol implementations will then be wrapped in high-level libraries with a nicer, more user-friendly API. High-level implementations are usually libraries that come with an API that doesn't expose SwiftNIO's ChannelPipeline and can therefore be used with very little (or no) SwiftNIO-specific knowledge. The implementations listed below do still do all of their I/O in SwiftNIO and integrate really well with the SwiftNIO ecosystem. SwiftNIO aims to support all of the platforms where Swift is supported. Currently, it is developed and tested on macOS and Linux. -
21
TSW
Tencent Server Web
A Node.js-based monitoring and debugging platform developed by Tencent, designed for large-scale applications and performance optimization. -
22
Takes
True object-oriented Java web framework without NULLs
Takes is a true object-oriented and immutable Java8 web development framework. Pay attention that UTF-8 encoding is set on the command line. The entire framework relies on your default Java encoding, which is not necessarily UTF-8 by default. To be sure, always set it on the command line with file.encoding Java argument. We decided not to hard-code "UTF-8" in our code mostly because this would be against the entire idea of Java localization, according to which a user always should have a choice of encoding and language selection. We're using Charset.defaultCharset() everywhere in the code. Essential part of Bigger Example is Front interface. It's encapsulates server's back-end and used to start an instance, which will accept requests and return results. FtBasic, which is a basic front, implements that interface. -
23
Tengine
A distribution of Nginx with some advanced features
Tengine is a web server originated by Taobao, the largest e-commerce website in Asia. It is based on the Nginx HTTP server and has many advanced features. Tengine has proven to be very stable and efficient on some of the top 100 websites in the world, including taobao.com and tmall.com. Tengine has been an open source project since December 2011. It is being actively developed by the Tengine team, whose core members are from Taobao, Sogou and other Internet companies. Tengine is a community effort and everyone is encouraged to get involved. All features of nginx-1.18.0 are inherited, i.e., it is 100% compatible with nginx. Support the CONNECT HTTP method for forward proxy. Support asynchronous OpenSSL, using hardware such as QAT for HTTPS acceleration. Enhanced operations monitoring, such as asynchronous log & rollback, DNS caching, memory usage, etc. Support server_name in Stream module. More load balancing methods, e.g., consistent hashing, and session persistence. -
24
Transitioner
A library for dynamic view-to-view transitions
Transitioner provides easy, dynamic, and adjustable animations between two views with nested children. -
25
UCall
Up to 100x Faster FastAPI. JSON-RPC with io_uring, SIMDJSON
Most modern networking is built either on slow and ambiguous REST APIs or unnecessarily complex gRPC. FastAPI, for example, looks very approachable. We aim to be equally or even simpler to use. It takes over a millisecond to handle a trivial FastAPI call on a recent 8-core CPU. In that time, light could have traveled 300 km through optics to the neighboring city or country, in my case. How does UCall compare to FastAPI and gRPC? How can a tiny pet-project with just a couple thousand lines of code compete with two of the most established networking libraries? UCall stands on the shoulders of Giants.
