Open Source Linux HTTP Clients - Page 3
Sort By:
HTTP Clients for Linux
View 1525 business solutions-
$300 Free Credits for Your Google Cloud ProjectsLaunch your next project with $300 in free Google Cloud credits—no strings attached. Test, build, and deploy without risk. Use your credits across the entire Google Cloud platform to find what works best for your needs. After your credits are used, continue with always-free tier services. Only pay when you're ready to scale. Sign up in minutes and start exploring.
-
Ship Agents FasterGemini Enterprise Agent Platform lets you rapidly build, scale, govern and optimize production-ready agents grounded in your organization's data. The platform enables developers to build custom or pre-built agents for virtually any use case. New customers get $300 in free credits.
-
1
Coraza
OWASP Coraza WAF is a golang modsecurity compatible firewall library
Coraza is an open-source, enterprise-grade, high-performance Web Application Firewall (WAF) ready to protect your beloved applications. It is written in Go, supports ModSecurity SecLang rulesets and is 100% compatible with the OWASP Core Rule Set. Coraza is a drop-in alternative to replace the soon-to-be abandoned Trustwave ModSecurity Engine and supports industry-standard SecLang rule sets. Coraza runs the OWASP Core Rule Set (CRS) to protect your web applications from a wide range of attacks, including the OWASP Top Ten, with a minimum of false alerts. CRS protects from many common attack categories including: SQL Injection (SQLi), Cross Site Scripting (XSS), PHP & Java Code Injection, HTTPoxy, Shellshock, Scripting/Scanner/Bot Detection & Metadata & Error Leakages. Coraza is a library at its core, with many integrations to deploy on-premise Web Application Firewall instances. -
2
This project has two parts. The first one is a hidden counter (using the 1x1 transparent pixel GIF) which registers into a MySQL database all remote IP addresses (whether IPv4 or IPv6), it tries very hard to use IPv6. The second part shows stats.
-
3
CppServer
Fast and low latency asynchronous socket server & client C++ library
Ultra-fast and low latency asynchronous socket server & client C++ library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols, and 10K connections problem solution. Cross platform (Linux, MacOS, Windows) Asynchronous communication. Supported CPU scalability designs: IO service per thread, thread pool. Supported transport protocols: TCP, SSL, UDP, UDP multicast. Supported Web protocols: HTTP, HTTPS, WebSocket, WebSocket secure. Supported Swagger OpenAPI iterative documentation. Supported message protocol based on Fast Binary Encoding. -
4
Dredd
Language-agnostic HTTP API Testing Tool
Dredd is a language-agnostic command-line tool for validating API description documents against the backend implementation of the API. Dredd reads your API description and step by step validates whether your API implementation replies with responses as they are described in the documentation. Dredd supports writing hooks — a glue code for each test setup and teardown. -
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
5
Drill
Drill is an HTTP load testing application written in Rust
Drill is an HTTP load-testing application written in Rust. The main goal for this project is to build a really lightweight tool as an alternative to other that require JVM and other stuff. You can write benchmark files, in YAML format, describing all the stuff you want to test. It was inspired by Ansible syntax because it is really easy to use and extend. As you can see, you can play with interpolations in different ways. This will let you specify a benchmark with different requests and dependencies between them. Right now, the easiest way to get drill is to go to the latest release page and download the binary file for your platform. OpenSSL is needed in order to compile Drill, whether it is through cargo install or when compiling from source with cargo build. -
6
A XML pull-parse library for Java 1.2, designed for processing XML protocol messages in the most efficient way possible. Contains a complete HTTP client library.
-
7
EGO
A simple and component-based microservice kit for go
EGO is a microservice-oriented governance framework implemented by golang, which integrates various engineering practices. Through the component-based design pattern, it is guaranteed that the business development can use various components in a unified way. For us engineers to improve component proficiency, we must first read a lot of open-source component documentation and code, and then insist on using it for a long time in order to form muscle memory and improve our speed of doing business. And the time and energy invested in all of this is enormous. To reduce this input cost and allow more developers to better use excellent open source components, EGO's approach is to standardize all open source components, encapsulate them, and unify various behaviors. -
8
Fast Android Networking
A Complete Fast Android Networking Library that also supports HTTP/2
Fast Android Networking Library is a powerful library for doing any type of networking in Android applications which is made on top of OkHttp Networking Layer. Fast Android Networking Library takes care of each and everything. So you don't have to do anything, just make a request and listen for the response. The recent removal of HttpClient in Android Marshmallow(Android M) made other networking libraries obsolete. No other single library does and everything like making requests, downloading any type of file, uploading file, loading images from the network in ImageView, etc. There are some libraries but they are outdated. No other library provides a simple interface for doing all types of things in networking like setting priority, canceling, etc. As it uses Okio , No more GC overhead in android applications. Okio is made to handle GC overhead while allocating memory. Okio does some clever things to save CPU and memory. -
9
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. -
Host LLMs in Production With On-Demand GPUsDeploy your model, get an endpoint, pay only for compute time. No GPU provisioning or infrastructure management required.
-
10
Flea2Flea is a pocket web server written in Java which enables ad-hoc peer-to-peer file sharing with anyone who has an http client (web browser). Files are only accessible while you are running Flea2Flea. You have absolute control.
-
11
Flurl
Fluent URL builder and testable HTTP client for .NET
Flurl is a modern, fluent, asynchronous, testable, portable, buzzword-laden URL builder and HTTP client library. Flurl is available on NuGet and is free for commercial use. It runs on a wide variety of platforms, including .NET Framework, .NET Core, Xamarin, and UWP. For just the URL builder, install Flurl. For everything else, install Flurl. You've come to the right place. Check out the docs. For programming question related to Flurl, please ask on Stack Overflow. Builder methods and their overloads are highly discoverable, intuitive, and always chainable. A few destructive methods are also included, such as RemoveQueryParam, RemovePathSegment, and ResetToRoot. Although similar to the parsing capabilities of System.Uri, Flurl aims to be more compliant with RFC 3986, and more true to the actual string provided. -
12
Google Data is a simple protocol for interacting with data on the web. Though it is possible to use these services with a simple HTTP client, this C++ (Qt) library provides helpful tools to streamline your code and keep up with server-side changes.
-
13
HTTP
Rust HTTP types
This crate is a general purpose library for common types found when working with the HTTP protocol. You’ll find Request and Response types for working as either a client or a server as well as all of their components. Notably you’ll find Uri for what a Request is requesting, a Method for how it’s being requested, a StatusCode for what sort of response came back, a Version for how this was communicated, and HeaderName/HeaderValue definitions to get grouped in a HeaderMap to work with request/response headers. You will notably not find an implementation of sending requests or spinning up a server in this crate. It’s intended that this crate is the “standard library” for HTTP clients and servers without dictating any particular implementation. Note that this crate is still early on in its lifecycle so the support libraries that integrate with the http crate are a work in progress! Stay tuned and we’ll be sure to highlight crates here in the future. -
14
Highly portable API written in C that implements the client side of the HTTP 1.1 Protocol as Defined in RFC 2616,2617. Can be easily ported to any platform that supports standard C calls and Berkeley sockets.
-
15
HTTP Client Plugin is an Eclipse 3.3+ plugin that enables users to construct and execute HTTP protocol messages. It is intended to support protocol level testing of web components.
-
16
HTTP Factories
Implementation of PSR-17 (HTTP Message Factories)
Implementation of PSR-17 (HTTP Message Factories) This repository holds all interfaces related to PSR-17 (HTTP Factories). Note that this is not a HTTP Factory implementation of its own. It is merely interfaces that describe the components of a HTTP Factory. The installable package and implementations are listed on Packagist. PSR-7 did not include a recommendation on how to create HTTP objects, which leads to difficulties when needing to create new HTTP objects within components that are not tied to a specific implementation of PSR-7. An HTTP factory is a method by which a new HTTP object, as defined by PSR-7, is created. HTTP factories MUST implement these interfaces for each object type that is provided by the package. -
17
HTTP Kit
Clojure HTTP server/client library with WebSocket support
http-kit is a minimalist, event-driven, high-performance Clojure HTTP server/client library with WebSocket and asynchronous support. A simple, high-performance event-driven HTTP client+server for Clojure. HTTP Kit is an (almost) drop-in replacement for the standard Ring Jetty adapter. So you can use it with all your current libraries (e.g. Compojure) and middleware. Using an event-driven architecture like Nginx, HTTP-kit is very, very fast. It comfortably handles tens of thousands of requests/sec on even midrange hardware. Here is another test about how it stacks up with others. It's not only fast, but efficient! Each connection costs nothing but a few kB of memory. RAM usage grows O(n) with connections. Written from the ground-up to be lean, the entire client/server is available as a single ~90kB JAR with zero dependencies and ~3k lines of (mostly Java) code. Synchronous is simple. Asynchronous is fast & flexible. -
18
HTTP Prompt
An interactive command-line HTTP and API testing client
HTTP Prompt is an interactive command-line HTTP client featuring autocomplete and syntax highlighting. You'll never have to memorize the whole commands and HTTP headers thanks to autocomplete with fuzzy matching. Improve readability by rendering JSON, HTML and commands with 27 builtin color themes, borrowed from Pygments. Designed to work with and built on top of HTTPie, HTTP Prompt makes a perfect companion for HTTPie. Cookie-based authentication made easy as incoming cookies are automatically set into your next request. With pipelines and output redirection, HTTP Prompt works seamlessly with your existing command line tools such as jq. Specify an OpenAPI/Swagger specification then you'll be able to explore API endpoints with ls like a filesystem. -
19
HTTP library for Lua
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0; client and server. -
20
HTTPSession will provide a complete java library to manage HTTP client sessions. The features (will) include: cookie management, HTTP authentication, referer management, navigation history, refresh statements and HTTP redirections handling.
-
21
HTTPlug
HTTPlug, the HTTP client abstraction for PHP
HTTPlug allows you to write reusable libraries that need an HTTP client without binding to a specific implementation. We provide adapters for existing HTTP Clients, so you can use your regular tools, even in compatible third-party packages. Furthermore, you can implement your own, if you would like to. Need to log each request? Authenticate a request? It's easy. Our powerful plugin system allows you to add custom logic to the request's lifecycle. This package also provides a synchronous HttpClient interface with the same method signature as the PSR-18 client. For synchronous requests, we recommend using PSR-18 directly. -
22
HTTPoison
Yet Another HTTP client for Elixir powered by hackney
HTTP client for Elixir, based on HTTPotion. HTTPoison uses hackney to execute HTTP requests instead of ibrowse. Using hackney we work only with binaries instead of string lists. First, add HTTPoison to your mix.exs dependencies. Add :httpoison to your applications list if your Elixir version is 1.3 or lower. You can also easily pattern match on the HTTPoison.Response struct. There are a number of supported options(not to be confused with the HTTP options method), documented here, that can be added to your request. The example below shows the use of the :ssl and :recv_timeout options for a post request to an api that requires a bearer token. The :ssl option allows you to set options accepted by the Erlang SSL module, and :recv_timeout sets a timeout on receiving a response, the default is 5000ms. -
23
Hoverfly
Lightweight service virtualization/ API simulation / API mocking tool
Hoverfly is a lightweight, open source API simulation tool. Using Hoverfly, you can create realistic simulations of the APIs your application depends on. Replace unreliable test systems and restrictive API sandboxes with high-performance simulations in seconds. Run on MacOS, Windows or Linux, or use native Java or Python language bindings to get started quickly. Simulate API latency or failure when required by writing custom scripts in the language of your choice. -
24
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. -
25
HttpClient component
Provides powerful methods to fetch HTTP resources synchronously
Provides powerful methods to fetch HTTP resources synchronously or asynchronously. The HttpClient component is a low-level HTTP client with support for both PHP stream wrappers and cURL. It provides utilities to consume APIs and supports synchronous and asynchronous operations. The HTTP client contains many options you might need to take full control of the way the request is performed, including DNS pre-resolution, SSL parameters, public key pinning, etc. They can be defined globally in the configuration (to apply it to all requests) and to each request (which overrides any global configuration). It's common that some of the HTTP client options depend on the URL of the request (e.g. you must set some headers when making requests to GitHub API but not for other hosts). If that's your case, the component provides scoped clients (using ScopingHttpClient) to autoconfigure the HTTP client based on the requested URL.
