Open Source HTTP Clients
Sort By:
HTTP Clients
View 9348 business solutionsBrowse free open source HTTP Clients and projects below. Use the toggles on the left to filter open source HTTP Clients by OS, license, language, programming language, and project status.
-
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.
-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
1
Gopeed
High speed downloader that supports all platforms
Gopeed (full name Go Speed), a high-speed downloader developed by Golang + Flutter, supports (HTTP, BitTorrent, Magnet) protocol, and supports all platforms. This project is divided into two parts, the front end uses flutter, the back end uses Golang, and the two sides communicate through the http protocol. On the unix system, unix socket is used, and on the windows system, tcp protocol is used. -
2
aria2
aria2 is a lightweight multi-protocol & multi-source download utility
aria2 is a lightweight multi-protocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink. aria2 can be manipulated via built-in JSON-RPC and XML-RPC interfaces. aria2 can download a file from multiple sources/protocols and tries to utilize your maximum download bandwidth. Really speeds up your download experience. aria2 doesn’t require much memory and CPU time. When disk cache is off, the physical memory usage is typically 4MiB (normal HTTP/FTP downloads) to 9MiB (BitTorrent downloads). CPU usage in BitTorrent with a download speed of 2.8MiB/sec is around 6%. aria2 supports The Metalink Download Description Format (aka Metalink v4), Metalink version 3, and Metalink/HTTP. Metalink offers the file verification, HTTP/FTP/SFTP/BitTorrent integration and various configurations for language, location, OS, etc. -
3
Jellyfin Android TV
Android TV Client for Jellyfin
Jellyfin Android TV is a Jellyfin client for Android TV, Nvidia Shield, and Amazon Fire TV devices. We welcome all contributions and pull requests! If you have a larger feature in mind please open an issue so we can discuss the implementation before you start. Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached. Your media, your server, your way. Jellyfin enables you to collect, manage, and stream your media. Run the Jellyfin server on your system and gain access to the leading free-software entertainment system, bells and whistles included. -
4
Webq83 Web Browser
W3 Web Browser
W3 Web Browser (WebQ83) – Linux amd64 & arm64 W3 is a lightweight and stable web browser developed for modern Linux distributions. It offers fast performance, low resource usage, and wide compatibility across various Linux systems. -
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
5
bombardier
Fast cross-platform HTTP benchmarking tool written in Go
bombardier is an HTTP(S) benchmarking tool. It is written in Go programming language and uses excellent fast HTTP instead of Go's default HTTP library, because of its lightning-fast performance. With bombardier v1.1 and higher, you can now use the net/HTTP client if you need to test HTTP/2.x services or want to use a more RFC-compliant HTTP client. -
6
HTTP Shortcuts for Android
Android app to create home screen shortcuts
A simple Android app that allows you to create shortcuts that can be placed on your home screen. Each shortcut, when clicked, triggers an HTTP request, with the possibility to process and display the response in various ways. Run arbitrary JavaScript before & after execution, which allows for lots of customization with features such as compute values such as timestamps, random numbers, UUIDs, hashes, HMACs, base64, etc. Parse JSON or XML and extract data from them. Show toast message or message dialogs. Vibrate or play notification sounds. Trigger other shortcuts to chain multiple HTTP requests. Interact with other devices and services by sending TCP or UDP packets, MQTT messages or using Wake-on-LAN. -
7
Restfox
Offline-first web HTTP client
Offline-first web HTTP client. Package available through snap can be installed using sudo snap install restfox. There are precompiled binaries in the releases page. -
8
WireMock.Net
WireMock.Net is a product for stubbing and mocking web HTTP responses
Free and Open Source tool for building mock APIs. Create stable development environments, isolate yourself from flakey 3rd parties and simulate APIs that don't exist yet. WireMock frees you from dependency on unstable APIs and allows you to develop with confidence. It's easy to launch a mock API server and simulate a host of real-world scenarios and APIs - including REST, SOAP, OAuth2 and more. WireMock is a free API mocking tool that can be run as a standalone server, or in a hosted version via the WireMock Cloud-managed service. API mocking involves creating a simple simulation of an API, accepting the same types of request and returning identically structured responses as the real thing, enabling fast and reliable development and testing. -
9
OwnTracks for Android
OwnTracks Android App
OwnTracks allows you to keep track of your own location. You can build your private location diary or share it with your family and friends. OwnTracks is open-source and uses open protocols for communication so you can be sure your data stays secure and private. This is the OwnTracks Android app. See our booklet for details on how to get started with OwnTracks, as well some details about behaviour specific to the Android app. -
Paessler: Easy to Use With Enterprise Power. Free TrialYou shouldn't have to choose between a monitoring tool that's easy to use and one that's powerful enough for a complex environment. PRTG's low-code interface lets any admin build dashboards, set alerts and monitor devices without scripting, while custom sensors and full API access are there when your team needs deeper control. One platform, no compromise. Download a free 30-day trial now.
-
10
AIOHTTP
Asynchronous HTTP client/server framework for asyncio and Python
Asynchronous HTTP Client/Server for asyncio and Python. AIOHTTP supports both client and server side of HTTP protocol. A long awaited new feature is tracing client request life cycle to figure out when and why client request spends a time waiting for connection establishment, getting server response headers etc. Now it is possible by registering special signal handlers on every request processing stage. The main change is dropping yield from support and using async/await everywhere. Farewell, Python 3.4. You often want to send some sort of data in the URL’s query string. If you were constructing the URL by hand, this data would be given as key/value pairs in the URL after a question mark, e.g. httpbin.org/get?key=val. Requests allows you to provide these arguments as a dict, using the params keyword argument. aiohttp internally performs URL canonicalization before sending request. -
11
Sub-Store
Advanced Subscription Manager for QX, Loon, Surge, Stash, etc.
Advanced subscription manager for QX, Loon, Surge, Stash and ShadowRocket. Conversion among various formats. Subscription formatting. Collect multiple subscriptions in one URL. -
12
TinyGSM
A small Arduino library for GSM modules, that just works
A small Arduino library for GSM modules that just works. This library is easy to integrate with lots of sketches that use Ethernet or WiFi. PubSubClient (MQTT), Blynk, HTTP Client, and File Download examples are provided. Arduino GSM library uses 15868 bytes (49%) of Flash and 1113 bytes (54%) of RAM in a similar scenario. TinyGSM also pulls data gently from the modem (whenever possible), so it can operate on very little RAM. Now, you have more space for your experiments. TCP (HTTP, MQTT, Blynk, ...) All modules support TCP connections. Most modules support multiple simultaneous connections. TCP and SSL connections can usually be mixed up to the total number of possible connections. Many GSM modems, WiFi, and radio modules can be controlled by sending AT commands over Serial. TinyGSM knows which commands to send, and how to handle AT responses, and wraps that into the standard Arduino Client interface. -
13
Titanium Web Proxy
A cross-platform asynchronous HTTP(S) proxy server in C#
A lightweight HTTP(S) proxy server written in C#. For programming help use StackOverflow with the tag Titanium-Web-Proxy. API Documentation and Wiki/Contribution guidelines. Multithreaded and asynchronous proxy employing server connection pooling, certificate cache, and buffer pooling. View, modify, redirect and block requests or responses. Supports mutual SSL authentication, proxy authentication & automatic upstream proxy detection. Supports kerberos, NTLM authentication over HTTP protocols on Windows domain-controlled networks. SOCKS4/5 Proxy support. Refer the HTTP Proxy Server library in your project and look up the test project to learn usage. -
14
HTTPX
A next generation HTTP client for Python
HTTPX is a fully featured HTTP client for Python 3, which provides sync and async APIs, and support for both HTTP/1.1 and HTTP/2. HTTPX should currently be considered in beta. A 1.0 release is expected to be issued sometime in 2021. International domains and URLs, keep-alive and connection pooling, sessions with cookie persistence, browser-style SSL verification. Basic/digest authentication, elegant key/value cookies, automatic decompression. Automatic content decoding, unicode response bodies, multipart file uploads, HTTP(S) proxy support. Connection timeouts, streaming downloads, .netrc support, and chunked requests. For more advanced topics, see the Advanced Usage section, the async support section, or the HTTP/2 section. The Developer Interface provides a comprehensive API reference. -
15
Pingora
A library for building fast, reliable and evolvable network services
Pingora is a Rust-based high-performance HTTP proxy and networking framework developed by Cloudflare to eventually replace NGINX. Designed for extreme reliability and memory-safe concurrency, it handles over 40 million requests per second in production and reduces CPU/memory usage significantly compared to traditional web servers. -
16
rathole
A lightweight and high-performance reverse proxy for NAT traversal
A secure, stable and high-performance reverse proxy for NAT traversal, written in Rust. rathole, like frp and ngrok, can help to expose the service on the device behind the NAT to the Internet, via a server with a public IP. High Performance Much higher throughput can be achieved than frp, and more stable when handling a large volume of connections. Low Resource Consumption Consumes much fewer memory than similar tools. See Benchmark. The binary can be as small as ~500KiB to fit the constraints of devices, like embedded devices as routers. Security Tokens of services are mandatory and service-wise. The server and clients are responsible for their own configs. With the optional Noise Protocol, encryption can be configured at ease. No need to create a self-signed certificate! TLS is also supported. -
17
urllib3
Python HTTP library with thread-safe connection pooling
urllib3 is a powerful, user-friendly HTTP client for Python. Much of the Python ecosystem already uses urllib3 and you should too. Thread safety, connection pooling. Client-side TLS/SSL verification. File uploads with multipart encoding. Helpers for retrying requests and dealing with HTTP redirects. Support for gzip, deflate, brotli, and zstd encoding. Proxy support for HTTP and SOCKS. 100% test coverage. Professional support for urllib3 is available as part of the Tidelift Subscription. Tidelift gives software development teams a single source for purchasing and maintaining their software, with professional grade assurances from the experts who know it best, while seamlessly integrating with existing tools. -
18
Axios
Promise based HTTP client for the browser and node.js
Axios is a promise-based HTTP client for the browser and Node.js. It makes sending asynchronous HTTP requests to REST endpoints and performing CRUD operations much easier. The Axios library can be used in plain JavaScript or with more advanced frameworks like Vue.js or React.js. -
19
Open Directory Downloader
Indexes open directories
Indexes open directories listings in 130+ supported formats, including FTP(S), Google Drive, Bhadoo, GoIndex, Go2Index (alternatives), Dropbox, Mediafire, GoFile, GitHub. Written in C# with .NET (Core), which means it is cross-platform! Downloading is not (yet) implemented, but is already possible when you use the resulting file into another tool (for most of the formats). When you are NOT using the self-contained releases, you need to install the latest/current Runtime version of .NET 7. -
20
sish
HTTP(S)/WS(S)/TCP Tunnels to localhost using only SSH
An open source serveo/ngrok alternative. Builds are made automatically for each commit to the repo and are pushed to Dockerhub. Builds are tagged using a commit sha, branch name, tag, latest if released on main. Each release builds separate sish binaries that can be downloaded from here for various OS/archs. Feel free to either use the automated binaries or to build your own. If you submit a PR, images are not built by default and will require a retag from a maintainer to be built. You can also use Docker Compose to setup your sish instance. This includes taking care of SSL via Let's Encrypt for you. This uses the adferrand/dnsrobocert container to handle issuing wildcard certifications over DNS. SSH can normally forward local and remote ports. This service implements an SSH server that only handles forwarding and nothing else. The service supports multiplexing connections over HTTP/HTTPS with WebSocket support. -
21
Feign
Make writing Java http clients easier
Feign is a Java to HTTP client binder that was built primarily to make writing Java http clients easier. Inspired by previous projects Retrofit, JAXRS-2.0 and WebSocket, Feign was designed to reduce the complexity that is often involved in binding the Denominator uniformly to HTTP APIs, no matter the ReSTfulness. Feign works by processing annotations into a templatized request, to which arguments are applied in a straightforward manner before output. While it may only support text-based APIs, it simplifies system aspects dramatically and makes it much easier to unit test your conversions. Feign makes use of great tools like Jersey and CXF for writing Java clients for ReST or SOAP services. It also lets you write your own code on top of http libraries, and connects your code to http APIs with little overhead. -
22
HTTP Toolkit
Electron wrapper to build and distribute HTTP Toolkit
HTTP Toolkit Desktop is an open-source application that packages HTTP Toolkit into a standalone debugging environment for Windows, macOS, and Linux. It uses Electron to combine the application's graphical interface with its underlying Node.js server. The software enables developers to intercept, inspect, and modify HTTP and HTTPS traffic from browsers, applications, and development environments. Users can analyze requests and responses, examine headers, and inspect structured message bodies. It supports interactive request editing, debugging breakpoints, and custom API requests. The desktop application automatically launches its background server and manages its lifecycle. With traffic interception and testing tools in one interface, HTTP Toolkit helps developers troubleshoot network communication and investigate application behavior. -
23
Faraday
Simple, but flexible HTTP client library, with support for backends
Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters (such as Net::HTTP) and embraces the concept of Rack middleware when processing the request/response cycle. You probably don't want to use Faraday directly in your project, as it will lack an actual client library to perform requests. Instead, you probably want to have a look at Awesome Faraday for a list of available adapters. The best starting point is the Faraday Website, with its introduction and explanation. This library aims to support and is tested against the currently officially supported Ruby implementations. This means that, even without a major release, we could add or drop support for Ruby versions, following their EOL. Currently that means we support Ruby 2.6+. You can also install the faraday_middleware extension gem to access a collection of useful Faraday middleware. -
24
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. -
25
Guzzle
An extensible PHP HTTP client
Guzzle is a PHP HTTP client that makes it easy to send HTTP requests and trivial to integrate with web services. Simple interface for building query strings, POST requests, streaming large uploads, streaming large downloads, using HTTP cookies, uploading JSON data, etc... Can send both synchronous and asynchronous requests using the same interface. Uses PSR-7 interfaces for requests, responses, and streams. This allows you to utilize other PSR-7 compatible libraries with Guzzle. Abstracts away the underlying HTTP transport, allowing you to write environment and transport agnostic code; i.e., no hard dependency on cURL, PHP streams, sockets, or non-blocking event loops. Middleware system allows you to augment and compose client behavior.
Open Source HTTP Clients Guide
Open source HTTP clients areprograms that enable users to send and receive data over the internet. These clients use Hypertext Transfer Protocol (HTTP) to communicate with web server applications. The source code of open source HTTP clients is usually available for free, allowing users to customize and modify the program as they like.
Open source HTTP client programs are typically designed to work with multiple protocols, such as FTP, Gopher, Telnet or SSH. This makes them ideal for many different types of applications and environments since they provide a single solution for managing different kinds of network connections. Additionally, open source HTTP clients can often be more secure than commercially-available solutions due to their ability to be tweaked according to individual needs and preferences.
When it comes to performance, most open source HTTP clients feature algorithms that minimize the number of requests sent out by the system in order to improve speed and reliability. Furthermore, most open source products are built with extensibility in mind meaning they offer an array of options which allow developers to customize how their product works or behaves when certain conditions are met – allowing them better control over their own projects' performance as well as security levels since many open sources have publicly visible code.
On top of this, popular open-source HTTP clients come packed with a wide range of features including support for cookies management; caching policies; SSL/TLS support; proxy control; content encoding settings; MIME type detection; character sets handling; parsing & formatting capabilities etc., thus making them suitable for creating powerful web-based applications that efficiently interact with remote servers and data stores over the Internet without having complex custom coding requirements from scratch..
What Features Do Open Source HTTP Clients Provide?
- HTTP Requests: Open source HTTP clients provide support for various types of requests, such as GET, POST, HEAD, PUT and DELETE. In addition to standard requests, some clients also offer support for other custom requests.
- Authentication: Most open source HTTP clients allow authentication using Basic or Digest authentication. This allows user credentials to be sent over a secured connection without revealing the password in plain text.
- Proxy Servers: Open source clients can use proxy servers when making connections. This enables them to access resources from behind a firewall or through an anonymizing network (such as Tor).
- Cookies: Some open source clients are able to save cookies that are received from web servers and re-submit them on subsequent requests. This makes it easier for sites to remember user preferences and settings between visits.
- SSL/TLS Support: Many open source clients include support for secure connections via SSL (Secure Sockets Layer) or TLS (Transport Layer Security). This ensures that all data transmitted between the client and server is encrypted, preventing eavesdropping by third parties.
- Data Compression: Most open source HTTP clients have the ability to negotiate data compression with web servers they make connections with. Compression reduces the size of transmitted data which makes downloading files faster and more efficient use of bandwidth.
Types of Open Source HTTP Clients
- cURL: cURL is an open source command-line tool and library for transferring data from or to a server using various protocols, such as HTTP, FTP, IMAP, SMTP, and SCP. It can be used to quickly download web pages or other files from remote servers as well as uploading local files to remote servers.
- libcurl: This is an open source C-based library that allows developers to write their own client applications that can make HTTP requests. It provides a wide range of features like supporting various transfer protocols (HTTP/2 and HTTPS) and authentication methods like NTLM. It also supports Advanced Encryption Standard (AES) encryption for secure transactions.
- Apache HttpClient: This is an open source java library which provides high level client API for interacting with web servers via the Hypertext Transfer Protocol (HTTP). It enables developers to easily send GET/POST requests along with parameter manipulation, cookies handling and authorization capabilities.
- Unirest: Unirest is an open-source lightweight Java library which facilitates making HTTP calls by providing objects representing responses without having the need for manual parsing. Using this library, it becomes easier for developers to build HTTP clients in different languages like nodejs, Java, PHP etc., quickly and efficiently using fewer lines of code compared to traditional approaches.
- Requests: Requests is a Python based HTTP Client Library which allows engineers to make easy and quick use of sending all kinds of HTTP requests including GET/POST/PUT etc., even though it doesn't include support for streaming large uploads like some other libraries do.
What Are the Advantages Provided by Open Source HTTP Clients?
- Cost Savings: Open source clients are free to download and use. This eliminates the need to purchase licenses or licenses from third-party vendors, resulting in significant cost savings over time.
- Flexibility: Customization is easy with open source clients since developers have access to the code and can modify it as needed. This provides added flexibility when developing applications, allowing for a wider choice of features and functionalities.
- Security: Open source clients employ multiple layers of security to ensure reliable data transfer and communication between two systems. These measures help protect against malicious attacks like malware and unauthorized eavesdropping on sensitive information.
- Ease of Use: Simplicity is key with many open source clients, making them user-friendly without sacrificing efficiency or effectiveness. The intuitive design makes programming tasks easier while providing an enjoyable experience along the way.
- Scalability: As new technologies become available, open source solutions are easily scalable by leveraging its adaptation capabilities. This allows users to take advantage of advancements without needing major overhauls down the line.
Types of Users That Use Open Source HTTP Clients
- Web Developers: These users typically use open source HTTP clients for web development. They may need to pull data from a remote server, debug issues in the network environment, create custom APIs and manage traffic on their websites.
- System Administrators: Open source HTTP clients are often used by system administrators who need to troubleshoot problems with a web server or website, test applications on either side of a firewall or generate reports related to performance.
- Network Engineers: Network engineers use these tools to diagnose problems with networks, such as finding bottlenecks causing slow speeds or authentication errors causing connection issues.
- Security Analysts: Security analysts often rely on open source HTTP clients because they can inspect requests and responses between two systems without disturbing the underlying network infrastructure.
- DevOps Professionals: These professionals often use the same types of tools as security analysts since they have similar tasks of inspecting requests and responses between different servers in order to monitor performance, prevent attacks and scale capacity quickly when needed.
How Much Do Open Source HTTP Clients Cost?
Open source HTTP clients are completely free, meaning there is no cost associated with them. This is part of what makes open source software so attractive; its free availability for all to use and modify as needed. The only cost associated with an open source HTTP client would be the time and effort spent into setting it up and configuring it properly. Additionally, depending on the open source license that has been applied to the software, you may need to adhere to certain rules when sharing any modifications made to the code or making any derived works. It should also be noted that if you hire a professional developer to assist in installing and configuring the open source client, then you will be responsible for paying their fees as well.
What Do Open Source HTTP Clients Integrate With?
Open source http clients can integrate with a variety of types of software. This includes applications such as web browsers and content management systems, which allow users to view and interact with websites over the internet. Other types of software that can interface with open source http clients include server-side scripting languages like PHP, client-side development frameworks such as AngularJS, and libraries for routing requests and responses between different parts of an application. Additionally, many tools for testing APIs like Selenium or JMeter can be connected to open source http clients in order to perform automated tests on web services. Finally, popular databases such as MySQL and MongoDB often have drivers that are compatible with open source HTTP clients, allowing them to be used together in applications.
Trends Related to Open Source HTTP Clients
- Increased Adoption: Open source http clients are becoming increasingly popular among developers, especially since they are free to use and often offer more features than paid options.
- Improved Security: Open source http clients are designed with greater security in mind, which makes them ideal for applications that require a high level of security.
- More Flexibility: Open source http clients offer a wide range of customization options, allowing developers to tailor the client to their specific needs.
- Better Integration with Other Technologies: Open source http clients can be integrated easily with other technologies, such as databases and web servers, making them ideal for larger projects.
- Lower Development Costs: Using open source http clients eliminates the need for expensive license fees associated with proprietary software solutions.
- Increased Reliability: Open source http clients have been developed by a large community of developers, which means that any issues or bugs can be quickly identified and addressed.
- Faster Performance: Open source http clients offer faster performance than their proprietary counterparts, which can result in significant time savings for developers.
Getting Started With Open Source HTTP Clients
Getting started with open source HTTP clients is a great way to access websites and other web-based services. It can also be an easy way to get more familiar with the technologies that power the networked world we live in.
The first step for getting started with open source HTTP clients is to choose one of the many available options. There are numerous popular open source projects that provide different types of HTTP clients, so it’s important to review them and decide which best meets your needs. Popular choices include cURL, Apache HttpClient, Unirest, Requests and Spring RestTemplate. Most of these tools have comprehensive documentation that walks you through the steps needed to install and configure them on your system.
Once you have chosen and installed an appropriate tool, configuring it should be relatively straightforward. Each program may require its own configuration parameters, but most will need basic details such as domain name or IP address of the server as well as port number used for communication between client and server. Additionally some programs may require credentials for secure connection such as username/password combinations or authorization tokens.
The next step is actually making requests from your environment using your favorite programming language or REST API test applications like Postman or SoapUI depending on how exactly you want your request processed - if at all. This usually involves writing code that builds a “request object” containing all necessary information about what type of request you want performed (e.g., GET or POST) plus any data required by the target resource as part of that specific call (e.g., query parameters). If everything is configured correctly this should result in receiving response from the remote resource which is then consumed by our application according to our usage scenario; this could range from simple logging/printing out results all way up to feeding data fetched into machine learning models etc.
Finally there are certain safeguards in place when dealing with sensitive data over public networks like HTTPS encryption; here proper configuration would involve setting protocols such as SSL/TLS appropriately depending on resources accessed being secured by them or not etc… Needless to say most lower level details (such as TLS connection establishment order) can usually be set automatically through frameworks etc, though doing so manually does offer more control should potentially difficult compatibility issues arise between systems involved in communication due variety of versions employed for example within each language's toolset library versions available up until application deployment etc…
That said before trying use open source HTTP clients make sure all possible security precautions were taken care of first since misuse might lead wrongfully expose private & confidential information albeit intentionally or unintentionally.
