Open Source Linux HTTP Clients - Page 7
Sort By:
HTTP Clients for Linux
View 1525 business solutions-
Train ML Models With SQL You Already KnowBuild and deploy ML models using familiar SQL. Automate data prep with built-in Gemini. Query 1 TB and store 10 GB free monthly.
-
Go from Code to Production URL in SecondsSkip the Kubernetes configs. Cloud Run handles HTTPS, scaling, and infrastructure automatically. Two million requests free per month.
-
1
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. -
2
httr
httr: a friendly http package for R
httr is superseded: only changes necessary to keep it on CRAN will be made. We recommend using httr2 instead. The aim of httr is to provide a wrapper for the curl package, customized to the demands of modern web APIs. Functions for the most important http verbs: GET(), HEAD(), PATCH(), PUT(), DELETE() and POST(). Automatic connection sharing across requests to the same website (by default, curl handles are managed automatically), cookies are maintained across requests, and an up-to-date root-level SSL certificate store is used. Requests return a standard reponse object that captures the http status line, headers and body, along with other useful information. Support for OAuth 1.0 and 2.0 with oauth1.0_token() and oauth2.0_token(). The demo directory has eight OAuth demos: four for 1.0 (twitter, vimeo, withings and yahoo) and four for 2.0 (facebook, github, google, linkedin). OAuth credentials are automatically cached within a project. -
3
hyper for Rust
An HTTP library for Rust
hyper is a fast HTTP implementation written in and for Rust. A Client for talking to web services. A Server for building those web services. Blazing fast thanks to Rust. High concurrency with non-blocking sockets. HTTP/1 and HTTP/2 support. hyper is a relatively low-level library, meant to be a building block for libraries and applications. If you are looking for a convenient HTTP client, then you may wish to consider reqwest. If you are looking for a convenient HTTP server, then you may wish to consider warp. Both are built on top of this library. A Service lets you define how to respond to incoming requests. While it is possible to implement the trait directly, there are a few patterns that are common when using Hyper. We’ve included some helpers for when these patterns fit our needs. An echo server will listen for incoming connections and send back the request body as the response body on POST requests. -
4
immortal
A *nix cross-platform (OS agnostic) supervisor
A *nix cross-platform (OS agnostic) supervisor. The main idea behind immortal is to keep up and running services forever even if the server is rebooted the service should be started and based on the requirements probably the services may start in sequence by waiting for others to start, wait some seconds before starting, etc, but at the end the idea remains, “run something forever” and in case exist just restart it. Doing this could be tricky, mainly because if you just want to launch your service/worker/daemon, etc you may not want to spend to much time understanding how to properly launch something in the operating system your company is using. Probably you just join a new team and when are about to deploy, found out that the production servers are not using the OS you were used to besides they don’t support/have your known supervisor, have a mix of init/upstart scripts. -
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.
-
5
json4sapnw
Another JSON extension for SAP ABAP
This is a SAP addon to handle JSON data within SAP ABAP Programs. It comes in the customer exchange namespace /CEX/ and has to be installed as an SAP transport request. The addon supports object oriented JSON methods to process deep structured JSON data. Building JSON data from SAP data objects and parsing JSON data back to SAP data objects are supported. See the WIKI for some examples. Thanks to the SAP community and especially to Rüdiger Plantiko for the basic work (http://ruediger-plantiko.blogspot.de/2010/12/ein-json-parser-in-abap.html). Enjoy! last Changes: - JSON HTTP Client - HTTP Auth for Basic, SAP Basic+SSO, WSSE - Bugfixes: Big Integer, negative Integer - Array with has_next/next - Object with robust set_text method - OpenWeatherMap.org Example (see files/example) -
6
ky
JavaScript HTTP client based on the browser Fetch API
Ky targets modern browsers and Deno. For older browsers, you will need to transpile and use a fetch polyfill and globalThis polyfill. For Node.js, check out Got. For isomorphic needs (like SSR), check out ky-universal. It's just a tiny file with no dependencies. Internally, the standard methods (GET, POST, PUT, PATCH, HEAD and DELETE) are uppercased in order to avoid server errors due to case sensitivity. Search parameters to include in the request URL. Setting this will override all existing search parameters in the input URL. After prefixUrl and input are joined, the result is resolved against the base URL of the page (if any). The hook can return a Request to replace the outgoing request, or return a Response to completely avoid making an HTTP request. This can be used to mock a request, check an internal cache, etc. An important consideration when returning a request or response from this hook is that any remaining beforeRequest hooks will be skipped. -
7
libhv
Network library for developing TCP/UDP/SSL/HTTP/WebSocket/MQTT client
Like libevent, libev, and libuv, libhv provides event loop with non-blocking IO and timer, but simpler api and richer protocols. Cross-platform (Linux, Windows, MacOS, BSD, Solaris, Android, iOS) High-performance EventLoop (IO, timer, idle, custom) TCP/UDP client/server/proxy. TCP supports heartbeat, reconnect, upstream, MultiThread-safe write and close, etc. Built-in common unpacking modes (FixedLength, Delimiter, LengthField) RUDP support: WITH_KCP. SSL/TLS support: (via WITH_OPENSSL or WITH_GNUTLS or WITH_MBEDTLS) HTTP client/server (support https http1/x http2 grpc). HTTP supports static service, indexof service, proxy service, sync/async API handler. HTTP supports RESTful, router, middleware, keep-alive, chunked, SSE, etc. WebSocket client/server. -
8
-
9
lua-resty-http
Lua HTTP client cosocket driver for OpenResty / ngx_lua
Lua HTTP client cosocket driver for OpenResty / ngx_lua. HTTP 1.0 and 1.1 SSL. Streaming interface to the response body, for predictable memory usage. Alternative simple interface for single-shot requests without a manual connection step. Chunked and non-chunked transfer encodings. Connection keepalives. Request pipelining. Trailers, HTTP proxy connections, and mTLS. -
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.
-
10
mango HTTP Client
Lightweight HTTP Client for embedded devices
mango is a free, open source, lightweight HTTP Client library written entirely in C. The focus of the mango implementation is to reduce resource usage while still providing an almost full-scale HTTP Client. This makes it suitable for use in memory-constrained embedded devices where memory and CPU power are at a premium. -
11
plow
A high-performance HTTP benchmarking tool
Plow is an HTTP(S) benchmarking tool, written in Golang. It uses excellent fast HTTP instead of Go's default net/http due to its lightning-fast performance. Plow runs at specified connections (option -c) concurrently and real-time records summary statistics, histogram of execution time and calculates percentiles to display on Web UI and terminal. It can run for a set duration( option -d), for a fixed number of requests(option -n), or until Ctrl-C is interrupted. The implementation of real-time computing Histograms and Quantiles using stream-based algorithms inspired by Prometheus with low memory and CPU bounds. so it's almost no additional performance overhead for benchmarking. -
12
r2
HTTP client, spiritual successor to request
Early in Node.js I wrote an HTTP client library called request. It evolved along with Node.js and eventually became very widely depended upon. A lot has changed since 2010 and I've decided to re-think what a simple HTTP client library should look like. This new library, r2, is a completely new approach from request. Rather than being built on top of the Node.js Core HTTP library and shimmed for the browser, r2 is built on top of the browser's Fetch API and shimmed for Node.js. APIs are meant to be used with async/await, which means they are based on promises. Being written to the Fetch API is a huge benefit for browser users. When running through browserify request is ~2M uncompressed and ~500K compressed. r2 is only 66K uncompressed and 16K compressed. -
13
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. -
14
req
Simple Go HTTP client with Black Magic
Simple and easy to use, providing rich client-level and request-level settings, all of which are intuitive and chainable methods. Provides powerful and convenient debug utilities, including debug logs, performance traces, and even dump the complete request and response content. API testing can be done with minimal code, no need to explicitly create any Request or Client, or even to handle errors. Detect and decode to utf-8 automatically if possible to avoid garbled characters (See Auto Decode), marshal request body and unmarshal response body automatically according to the Content-Type. Req support HTTP/1.1, HTTP/2, and HTTP/3, and can automatically detect the server side and select the optimal HTTP version for requests, you can also force the protocol if you want. Support automatic request retry and is fully customizable. -
15
requests-cache
Persistent HTTP cache for python requests
requests-cache is a persistent HTTP cache that provides an easy way to get better performance with the Python requests library. Keep using the requests library you’re already familiar with. Add caching with a drop-in replacement for requests. The session, or install globally to add transparent caching to all request functions. Get sub-millisecond response times for cached responses. When they expire, you still save time with conditional requests. Works with several storage backends including SQLite, Redis, MongoDB, and DynamoDB; or save responses as plain JSON files, YAML, and more. Use Cache-Control and other standard HTTP headers, define your own expiration schedule, and keep your cache clutter-free with backends that natively support TTL or any combination of strategies. Works out of the box with zero config, but with a robust set of features for configuring and extending the library to suit your needs. -
16
reqwest
An easy and powerful Rust HTTP Client
The reqwest crate provides a convenient, higher-level HTTP client. It handles many of the things that most people just expect an HTTP client to do for them. The reqwest::Client is asynchronous. For applications wishing to only make a few HTTP requests, the reqwest::blocking API may be more convenient. There are several ways you can set the body of a request. The basic one is by using the body() method of a RequestBuilder. This lets you set the exact raw bytes of what the body should be. -
17
schema
Package gorilla/schema fills a struct with form values
Package gorilla/schema converts structs to and from form values. Conversely, the contents of a struct can be encoded into form values. To define custom names for fields, use a struct tag "schema". To not populate certain fields, use a dash for the name and it will be ignored. -
18
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. -
19
sttp client
The Scala HTTP client you always wanted
sttp client is an open-source library that provides a clean, programmer-friendly API to describe HTTP requests and how to handle responses. Requests are sent using one of the backends, which wrap other Scala or Java HTTP client implementations. The backends can integrate with a variety of Scala stacks, providing both synchronous and asynchronous, procedural and functional interfaces. Backend implementations include ones based on akka-http, http4s, OkHttp, and HTTP clients which ship with Java. They integrate with Akka, Monix, fs2, cats-effect, scalaz and ZIO. Supported Scala versions include 2.11, 2.12, 2.13 and 3, Scala.JS and Scala Native. -
20
tus resumable upload protocol
Open Protocol for Resumable File Uploads
People are sharing more and more photos and videos every day. Mobile networks remain fragile, however. Platform APIs are also often a mess and every project builds its own file uploader. There are a thousand one-week projects that barely work when all we need is one real project. One project was done right. We are the ones who are going to do this right. Our aim is to solve the problem of unreliable file uploads once and for all. tus is a new open protocol for resumable uploads built on HTTP. It offers simple, cheap, and reusable stacks for clients and servers. It supports any language, any platform, and any network. It may seem to be an impossible dream. Perhaps that is because no-one has managed to solve it yet. Still, we are confident and we are going to give it our best shot. Join us on GitHub and help us make the world a better place. -
21
tus-js-client
A pure JavaScript client for the tus resumable upload protocol
tus-js-client is a JavaScript client for the tus resumable upload protocol, enabling reliable and efficient file uploads, especially for large files or unstable network conditions. -
22
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. -
23
vue-resource
The HTTP client for Vue.js
vue-resource is a plugin for Vue.js which provides services for making web requests and handle responses using a XMLHttpRequest or JSONP. You can install it via yarn or NPM. Available on jsdelivr, unpkg or cdnjs. Typescript for vue-resource should work out of the box since the type definition files are included within the npm package. The http service can be used globally Vue.http or in a Vue instance this.$http. A Vue instance provides the this.$http service which can send HTTP requests. A request method call returns a Promise that resolves to the response. Also the Vue instance will be automatically bound to this in all function callbacks. Shortcut methods are available for all request types. These methods work globally or in a Vue instance. The Recipes provide code examples to common use-cases. If you want to share your recipe feel free to send a pull request. -
24
wechat-bot
PC WeChat chat robot with secondary development interface
The client sends a friend text message (supports websocket and HTTP). The client obtains the wxid and name of the friend in the address book (supports websocket and HTTP). The client sends a picture to a friend (supports websocket and HTTP). Sends an AT message (support websocket and HTTP). Send attachments (only support HTTP, weboscket). Get chatroom member list (wxid) and nickname (support websocket and HTTP). Please refer to the sample code of client.js (websocket client) and httpclient.js (http client). You can inject it once. If you want to re-inject, please exit WeChat, restart WeChat and then inject it. -
25
acl_cpp
a powerfull c++ library for win32/linux, server framework, HttpServlet
acl_cpp(which has been included in acl project: https://sourceforge.net/projects/acl/ , please download it from acl project url) is a c++ wrap library for acl, and acl_cpp has many more useful functions than acl, such as streaming mime parsing, handler socket supporting, and db(mysql and sqlite) pool interface, HttpServlet, etc. With acl_cpp, you'll get more powerfull acl functions, and the quickly development, module programming, good luck!
