Open Source Mac HTTP Clients - Page 6
Sort By:
HTTP Clients for Mac
View 1595 business solutions-
HubSpot is an AI-powered customer platform with all the software, integrations, and resources you need to connect your marketing, sales, and customer service. HubSpot's connected platform enables you to grow your business faster by focusing on what matters most: your customers.
-
SKUDONET ADC, operates at the application layer, efficiently distributing network load and application load across multiple servers. This not only enhances the performance of your application but also ensures that your web servers can handle more traffic seamlessly.
-
1
axios-extensions
axios extensions lib, including throttle, cache, retry features etc.
A non-invasive, simple, reliable collection of axios extension. It is highly recommended to enable the request logging recorder in the development environment(disabled by default). Besides configuring the request through the cacheAdapterEnhancer, we can enjoy more advanced features via configuring every individual request. -
2
baloo
Expressive end-to-end HTTP API testing made easy in Go
Expressive and versatile end-to-end HTTP API testing made easy in Go (golang), built on top of the gentleman HTTP client toolkit. -
3
casync
Content-addressable data synchronization tool
A combination of the rsync algorithm and content-addressable storage. An efficient way to store and retrieve multiple related versions of large file systems or directory trees. An efficient way to deliver and update OS, VM, IoT and container images over the Internet in an HTTP and CDN friendly way. Let's take a large linear data stream, split it into variable-sized chunks (the size of each being a function of the chunk's contents), and store these chunks in individual, compressed files in some directory, each file named after a strong hash value of its contents, so that the hash value may be used to as key for retrieving the full chunk data. Let's call this directory a "chunk store". At the same time, generate a "chunk index" file that lists these chunk hash values plus their respective chunk sizes in a simple linear array. The chunking algorithm is supposed to create variable, but similarly sized chunks from the data stream. -
4
ciao
HTTP checks & tests (private & public) monitoring
HTTP checks & tests (private & public) monitoring - check the status of your URL. ciao checks HTTP(S) URL endpoints for a HTTP status code (or errors on the lower TCP stack) and sends a notification on status change via E-Mail or Webhooks. It uses Cron syntax to schedule the checks and comes along with a Web UI and a RESTful JSON API. Create an open-source web application for checking URL statuses with a UI and a REST API which is easy to install and maintain (no external dependencies like Databases, Caches, etc.) in public and private environments. -
When it comes to cybersecurity, what your clients don’t know can really hurt them. And believe it or not, keep them safe starts with asking questions. With ConnectWise Identify Assessment, get access to risk assessment backed by the NIST Cybersecurity Framework to uncover risks across your client’s entire business, not just their networks. With a clearly defined, easy-to-read risk report in hand, you can start having meaningful security conversations that can get you on the path of keeping your clients protected from every angle. Choose from two assessment levels to cover every client’s need, from the Essentials to cover the basics to our Comprehensive Assessment to dive deeper to uncover additional risks. Our intuitive heat map shows you your client’s overall risk level and priority to address risks based on probability and financial impact. Each report includes remediation recommendations to help you create a revenue-generating action plan.
-
5
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. -
6
dio
A powerful HTTP client for Dart and Flutter
A powerful HTTP client for Dart and Flutter, which supports global settings, Interceptors, FormData, aborting and canceling a request, files uploading and downloading, requests timeout, custom adapters, etc. -
7
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. -
8
elastic4s
Elasticsearch Scala Client - Reactive, Non Blocking, Type Safe, HTTP
Elastic4s is a concise, idiomatic, reactive, type safe Scala client for Elasticsearch. The official Elasticsearch Java client can of course be used in Scala, but due to Java's syntax it is more verbose and it naturally doesn't support classes in the core Scala core library nor Scala idioms such as typeclass support. Elastic4s's DSL allows you to construct your requests programatically, with syntactic and semantic errors manifested at compile time, and uses standard Scala futures to enable you to easily integrate into an asynchronous workflow. The aim of the DSL is that requests are written in a builder-like way, while staying broadly similar to the Java API or Rest API. Each request is an immutable object, so you can create requests and safely reuse them, or further copy them for derived requests. Because each request is strongly typed your IDE or editor can use the type information to show you what operations are available for any request type. -
9
faasd
A lightweight & portable faas engine
faasd is OpenFaaS reimagined but without the cost and complexity of Kubernetes. It runs on a single host with very modest requirements, making it fast and easy to manage. Under the hood it uses containers and Container Networking Interface (CNI) along with the same core OpenFaaS components from the main project. To deploy microservices and functions that you can update and monitor remotely. When you don't have the bandwidth to learn or manage Kubernetes. To deploy embedded apps in IoT and edge use-cases. To distribute applications to a customer or client. You have a cost sensitive project - run faasd on a 1GB VM for 5-10 USD / mo or on your Raspberry Pi. When you just need a few functions or microservices, without the cost of a cluster. -
Out-of-the-box scripts. Around-the-clock monitoring. Unmatched automation capabilities. Start doing more with less and exceed service delivery expectations.
-
10
find-my-way
A crazy fast HTTP router
A crazy fast HTTP router, internally uses a highly performant Radix Tree (aka compact Prefix Tree), supports route params, wildcards, and it's framework is independent. You can set a custom length for parameters in parametric (standard, regex and multi) routes by using maxParamLength option, the default value is 100 characters. If you are using a regex-based route, find-my-way will throw an error if detects potentially catastrophic exponential-time regular expressions (internally uses safe-regex2). According to RFC3986, find-my-way is case-sensitive by default. You can disable this by setting the caseSensitive option to false: in that case, all paths will be matched as lowercase, but the route parameters or wildcards will maintain their original letter casing. -
11
gentleman
Plugin-driven, extensible HTTP client toolkit for Go
Full-featured, plugin-driven, middleware-oriented toolkit to easily create rich, versatile and composable HTTP clients in Go. gentleman embraces extensibility and composition principles in order to provide a flexible way to easily create featured HTTP client layers based on built-in or third-party plugins that you can register and reuse across HTTP clients. As an example, you can easily provide retry policy capabilities or dynamic server discovery in your HTTP clients simply attaching the retry or consul plugins. Take a look to the examples, list of supported plugins, HTTP entities or middleware layer to get started. For testing purposes, see baloo, a utility library for expressive end-to-end HTTP API testing, built on top of gentleman toolkit. For HTTP mocking, see gentleman-mock, which uses gock under the hood for easy and expressive HTTP client request mocking. -
12
hackney
simple HTTP client in Erlang
hackney is an HTTP client library for Erlang. No message passing (except for asynchronous responses): response is directly streamed to the current process and state is kept in a #client{} record. Binary streams, SSL support, keepalive handling, basic authentication. Stream the response and the requests, fetch a response asynchronously, multipart support (streamed or not), and chunked encoding support. It can send files using the sendfile API. Optional socket pool, REST syntax, hackney, Method(URL) (where a method can get, post, put, delete, ...) -
13
http 0.13.6
A composable API for making HTTP requests in Dart
A composable, Future-based library for making HTTP requests. This package contains a set of high-level functions and classes that make it easy to consume HTTP resources. It's multi-platform and supports mobile, desktop, and browser. The easiest way to use this library is via the top-level functions. They allow you to make individual HTTP requests with minimal hassle. If you're making multiple requests to the same server, you can keep open a persistent connection by using a Client rather than making one-off requests. You can also exert more fine-grained control over your requests and responses by creating Request or StreamedRequest objects yourself and passing them to Client.send. This package is designed to be composable. This makes it easy for external libraries to work with one another to add behavior to it. Libraries wishing to add behavior should create a subclass of BaseClient that wraps another Client and adds the desired behavior. -
14
http-client-3-wrapper
Java wrapper around the old commons-http-client.3.1
This is a java wrapper around the old commons-http-client.3.1 HTTP client which not developed anymore. The wrapper is using the new HttpClient 4.x and keeps binary compatibility. The intention for developing this wrapper was using Axis 2 for accessing a Microsoft Exchange 2010 server which requires a NTLM2 authentication. Not all methods are implemented, but it works for me. Just remove the old commons-httpclient-3.1.jar and add http-client-3-wrapper to your project. -
15
http4k
The Functional toolkit for Kotlin HTTP applications
http4k is a lightweight but fully-featured HTTP toolkit written in pure Kotlin that enables the serving and consuming of HTTP services in a functional and consistent way. http4k applications are just Kotlin functions. http4k consists of a lightweight core library, http4k-core, providing a base HTTP implementation and Server/Client implementations based on the JDK classes. Further servers, clients, serverless, templating, websockets capabilities are then implemented in add-on modules. http4k apps can be simply mounted into a running Server, Serverless platform, or compiled to GraalVM and run as a super-lightweight binary. Apart the from Kotlin StdLib, http4k-core module has ZERO dependencies and weighs in at ~1mb. Add-on modules only have dependencies required for specific implementation. -
16
httpexpect
End-to-end HTTP and REST API testing for Go
Concise, declarative, and easy-to-use end-to-end HTTP and REST API testing for Go (golang). Basically, httpexpect is a set of chainable builders for HTTP requests and assertions for HTTP responses and payload, on top of net/http and several utility packages. URL path construction, with simple string interpolation provided by go-interpol package. URL query parameters (encoding using go-querystring package). Headers, cookies, payload: JSON, urlencoded or multipart forms (encoding using form package), plain text. Custom reusable request builders and request transformers. Type-specific assertions, supported types: object, array, string, number, boolean, null, datetime. Regular expressions. Simple JSON queries (using subset of JSONPath), provided by jsonpath package. JSON Schema validation, provided by gojsonschema package. -
17
A comprehensive HTTP client library for Python, httplib2 supports many features left out of other HTTP libraries such as HTTPS, caching, keep-alive, compression, redirects and authentication. Downloads are handled from the project home page.
-
18
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. -
19
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. -
20
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. -
21
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) -
22
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. -
23
-
24
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. -
25
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.