Open Source HTTP Clients
Sort By:
HTTP Clients
View 8892 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.
-
Build Agents and Models on One PlatformGemini Enterprise Agent Platform is Google Cloud's comprehensive platform for developers to build, scale, govern, and optimize agents and models. Choose from Google's most advanced models and third-party models like Anthropic's Claude Model Family.
-
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.
-
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
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. -
3
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. -
4
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. -
Error to trace to log to deploy. One click. No SSH.AppSignal links every error to the trace, the trace to the log, the log to the deploy that shipped it.
-
5
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. -
6
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. -
7
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. -
8
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. -
9
undici
An HTTP/1.1 client, written from scratch for Node.js
An HTTP/1.1 client, written from scratch for Node.js. This section documents our most commonly used API methods. Additional APIs are documented in their own files within the docs folder and are accessible via the navigation list on the left side of the docs site. Garbage collection in Node is less aggressive and deterministic (due to the lack of clear idle periods that browsers have through the rendering refresh rate) which means that leaving the release of connection resources to the garbage collector can lead to excessive connection usage, reduced performance (due to less connection re-use), and even stalls or deadlocks when running out of connections. -
Save Up to 91% on Cloud Compute With Spot VMsRun batch jobs at 60-91% off with Spot VMs. Long-running workloads get automatic discounts with sustained use.
-
10
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. -
11
HTTPie Desktop
Cross-platform API testing client for humans
HTTPie Desktop is a graphical API client built on top of the popular HTTPie terminal tool, offering a user-friendly interface for testing and interacting with APIs. It combines the simplicity of HTTPie’s CLI with a modern desktop and web UI for a more visual workflow. Developers can easily build, send, and preview HTTP requests without needing to memorize commands or write scripts. The platform supports organizing work into spaces, collections, and tabs, making it ideal for managing multiple APIs and projects. It also includes AI-assisted features to help streamline request creation and improve productivity. Overall, HTTPie Desktop provides a clean, intuitive, and powerful environment for API development across devices. -
12
RestSharp
Simple REST and HTTP API Client for .NET
RestSharp is probably the most popular HTTP client library for .NET. Featuring automatic serialization and deserialization, request and response type detection, variety of authentications and other useful features, it is being used by hundreds of thousands of projects. RestSharp passed over 32 million downloads on NuGet, with average daily download count of 10,000. It's being used by many popular OSS projects, including Roslyn and Swagger. The main purpose of RestSharp is to make synchronous and asynchronous calls to remote resources over HTTP. As the name suggests, the main audience of RestSharp are developers who use REST APIs. However, RestSharp can call any API over HTTP (but not HTTP/2), as long as you have the resource URI and request parameters that you want to send comply with W3C HTTP standards. RestSharp can take care of serializing the request body to JSON or XML and deserialize the response. It can also form a valid request URI based on different parameter kinds. -
13
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. -
14
cross-fetch
Universal WHATWG Fetch API for Node, Browsers and React Native
Universal WHATWG Fetch API for Node, Browsers and React Native. The scenario that cross-fetch really shines is when the same JavaScript codebase needs to run on different platforms. Platform agnostic, browsers, Node or React Native. Optional polyfill, it's up to you if something is going to be added to the global object or not. Simple interface, no instantiation, no configuration and no extra dependency. WHATWG compliant, it works the same way wherever your code runs. TypeScript support, better development experience with types. -
15
httplog
Log outgoing HTTP requests in ruby
Log outgoing HTTP requests made from your application. Helps with debugging pesky API error responses, or just generally understanding what's going on under the hood. In theory, it should also work with any library built on top of these. But the difference between theory and practice is bigger in practice than in theory. This is very much a development and debugging tool; it is not recommended to use this in a production environment as it is monkey-patching the respective HTTP implementations. You have been warned - use at your own risk. Just like in Rails, you can filter the values of sensitive parameters by setting the filter_parameters to an array of (lower case) keys. The value for "password" is filtered by default. Please note that this will only filter the request data with well-formed parameters (in the URL, the headers, and the request data) but not the response. It does not currently filter JSON request data either, just standard "key=value" pairs in the request body. -
16
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. -
17
HTTP Client
Async HTTP/1.1+2 client for PHP based on Amp
This package provides an asynchronous HTTP client for PHP based on Amp. Its API simplifies standards-compliant HTTP resource traversal and RESTful web service consumption without obscuring the underlying protocol. The library manually implements HTTP over TCP sockets; as such it has no dependency on ext/curl. Streams entity bodies for memory management with large transfers. Supports all standard and custom HTTP method verbs. Simplifies HTTP form submissions. Implements secure-by-default TLS. Supports cookies and sessions. Functions seamlessly behind HTTP proxies. Additionally, you might want to install the nghttp2 library to take advantage of FFI to speed up and reduce the memory usage on PHP 7.4. More extensive code examples reside in the examples directory. -
18
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. -
19
Rouille
Web framework in Rust
Rouille is a micro-web-framework library. It creates a listening socket and parses incoming HTTP requests from clients, then gives you the hand to process the request. Rouille was designed to be intuitive to use if you know Rust. Contrary to express-like frameworks, it doesn't employ middlewares. Instead, everything is handled in a linear way. Concepts closely related to websites (like cookies, CGI, form input, etc.) are directly supported by rouille. More general concepts (like database handling or templating) are not directly handled, as they are considered orthogonal to the microweb framework. However, rouille's design makes it easy to use in conjunction with any third-party library without the need for any glue code. The rouille library just ignores this optimization and focuses on providing an easy-to-use synchronous API instead, where each request is handled in its own dedicated thread. -
20
distribyted
Torrent client with HTTP, fuse, and WebDAV interfaces
Distribyted is an alternative torrent client. It can expose torrent files as a standard FUSE mount or webDAV endpoint and download them on demand, allowing random reads using a fixed amount of disk space. Distribyted supports several ways to expose the files to the user or external applications. Applications that supports WebDAV can access torrent files using this protocol. It is recommended when distribyted is running in a remote machine or using docker. Distribyted can show some kind of files directly as folders, making it possible for applications to read only the parts that they need. Here is a list of supported, to-be-supported, and not supported formats. Play multimedia files on your favorite video or audio player. These files will be downloaded on demand and only the needed parts. -
21
JETTY HAS MOVED TO ECLIPSE!!!! The latest releases of Jetty are hosted from http://eclipse.org/jetty. Jetty is an open-source project providing a HTTP server, HTTP client and javax.servlet container.
-
22
Cookie Parser
Parse HTTP request cookies
Parse Cookie header and populate req.cookies with an object keyed by the cookie names. Optionally you may enable signed cookie support by passing a secret string, which assigns req.secret so it may be used by other middleware. A middleware for Express.js that parses cookies from HTTP requests and makes them accessible in req.cookies. -
23
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. -
24
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. -
25
Jimp
An image processing library written entirely in JavaScript for Node
An image processing library for Node written entirely in JavaScript, with zero native dependencies. If you're using this library with TypeScript the method of importing slightly differs from JavaScript. Instead of using require, you must import it with ES6 default import scheme. If you're using a web bundles (webpack, rollup, parcel) you can benefit from using the module build of jimp. Using the module build will allow your bundler to understand your code better and exclude things you aren't using. If you're using webpack you can set process.browser to true and your build of jimp will exclude certain parts, making it load faster. The static Jimp.read method takes the path to a file, URL, dimensions, a Jimp instance or a buffer and returns a Promise. In some cases, you need to pass additional parameters with an image's URL.
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.
