Open Source ChromeOS HTTP Clients
Sort By:
HTTP Clients for ChromeOS
Browse free open source HTTP Clients and projects for ChromeOS 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.
-
Automate contact and company data extractionGenerate leads at scale without building or maintaining scrapers. Use 10,000+ ready-made tools that handle authentication, pagination, and anti-bot protection. Pull data from business directories, social profiles, and public sources, then export to your CRM or database via API. Schedule recurring extractions, enrich existing datasets, and integrate with your workflows.
-
1
Coraza
OWASP Coraza WAF is a golang modsecurity compatible firewall library
Coraza is an open-source, enterprise-grade, high-performance Web Application Firewall (WAF) ready to protect your beloved applications. It is written in Go, supports ModSecurity SecLang rulesets and is 100% compatible with the OWASP Core Rule Set. Coraza is a drop-in alternative to replace the soon-to-be abandoned Trustwave ModSecurity Engine and supports industry-standard SecLang rule sets. Coraza runs the OWASP Core Rule Set (CRS) to protect your web applications from a wide range of attacks, including the OWASP Top Ten, with a minimum of false alerts. CRS protects from many common attack categories including: SQL Injection (SQLi), Cross Site Scripting (XSS), PHP & Java Code Injection, HTTPoxy, Shellshock, Scripting/Scanner/Bot Detection & Metadata & Error Leakages. Coraza is a library at its core, with many integrations to deploy on-premise Web Application Firewall instances. -
2
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. -
3
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. -
4
POCO C++ Libraries
Cross-platform C++ libraries with a network/internet focus.
NOTE: Current source code as well as bugs/patches are on GitHub: https://github.com/pocoproject/poco/ C++ class libraries for network-centric, portable applications, integrated perfectly with the C++ Standard Library. Includes network protocols (Sockets, HTTP, FTP, SMTP, POP3, etc.), SQL database access and XML parsing. Licensed under Boost license. -
Automated RMM Tools | RMM SoftwareOut-of-the-box scripts. Around-the-clock monitoring. Unmatched automation capabilities. Start doing more with less and exceed service delivery expectations.
-
5
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.
-
6
Highly portable API written in C that implements the client side of the HTTP 1.1 Protocol as Defined in RFC 2616,2617. Can be easily ported to any platform that supports standard C calls and Berkeley sockets.
-
7
NetTool is a developer tool for monitoring and manipulating application-level network messages, particularly useful for debugging web applications and web services. There are two components to NetTool: the HTTP Client, and the TCP Tunnel.
-
8
Angular Websocket
The missing Angular WebSocket module for connecting client apps
Angular Websocket is a WebSocket service tailored for AngularJS 1.x applications, exposed primarily through the $websocket factory in the ngWebSocket module. It wraps the native WebSocket API in a way that plays nicely with Angular’s digest cycle, ensuring that UI updates are triggered when messages arrive. The library manages an internal send queue so that messages requested before the socket is open are safely sent once the connection is ready. It offers a set of convenience methods and callbacks, such as onMessage, onOpen, onClose, and onError, to keep WebSocket handling consistent with other Angular services. Developers can filter messages by string or regular expression and optionally disable automatic $digest calls when needed for performance. The project can be consumed via Bower, npm, CDN, or manual download, making it easy to introduce into legacy build setups. It aims to be the “missing WebSocket module” for AngularJS. -
9
Brynet
A Header-Only cross-platform C++ TCP network library
Header Only Cross-platform high-performance TCP network library using C++ 11. The server uses two network threads and one logic thread, the client uses one network (also process logic) thread. Every packet size is 46 bytes. Every packet contains the client's id. Server broadcast packets to all clients when recv one packet from any client. The client sends one packet when recv packet from the server and the packet's id is equal self. -
Reach Your Audience with Rise Vision, the #1 Cloud Digital Signage Software SolutionRise Vision is the #1 digital signage company, offering easy-to-use cloud digital signage software compatible with any player across multiple screens. Forget about static displays. Save time and boost sales with 500+ customizable content templates for your screens. If you ever need help, get free training and exceptionally fast support.
-
10
This project aims to come up with a comprehensive cross-platform library of networking routines for inclusion in the Boost C++ Library.
-
11
A Java library that provides accelerated downloads of HTTP/HTTPS URIs via the GET and POST methods. Works similar to download managers as requests are made in parallel and chunked for speed.
-
12
Cicada
Fast lightweight HTTP service framework
Fast, lightweight Web framework based on Netty; without too much dependency, and the core jar package is only 30KB. Configuration files can also be read in multiple environments, just add VM parameters, also ensure that the parameter name and file name are consistent. -
13
CppServer
Fast and low latency asynchronous socket server & client C++ library
Ultra-fast and low latency asynchronous socket server & client C++ library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols, and 10K connections problem solution. Cross platform (Linux, MacOS, Windows) Asynchronous communication. Supported CPU scalability designs: IO service per thread, thread pool. Supported transport protocols: TCP, SSL, UDP, UDP multicast. Supported Web protocols: HTTP, HTTPS, WebSocket, WebSocket secure. Supported Swagger OpenAPI iterative documentation. Supported message protocol based on Fast Binary Encoding. -
14
Dredd
Language-agnostic HTTP API Testing Tool
Dredd is a language-agnostic command-line tool for validating API description documents against the backend implementation of the API. Dredd reads your API description and step by step validates whether your API implementation replies with responses as they are described in the documentation. Dredd supports writing hooks — a glue code for each test setup and teardown. -
15
Finch
Scala combinator library for building Finagle HTTP services
Finch is a thin layer of purely functional basic blocks atop of Finagle for building composable HTTP APIs. Its mission is to provide the developers with simple and robust HTTP primitives being as close as possible to the bare metal Finagle API. -
16
Flea2Flea is a pocket web server written in Java which enables ad-hoc peer-to-peer file sharing with anyone who has an http client (web browser). Files are only accessible while you are running Flea2Flea. You have absolute control.
-
17
HTTP library for Lua
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0; client and server. -
18
HTTPSession will provide a complete java library to manage HTTP client sessions. The features (will) include: cookie management, HTTP authentication, referer management, navigation history, refresh statements and HTTP redirections handling.
-
19
HyperCES
Hyper Cookie Encapsulation System
HyperCES is a Cookie Encapsulation System (CES). The purpose of a CES is to act as an intermediary between an HTTP client and a web server, to handle cookies on the client's behalf. HyperCES does this by adding a session identifier to the URL. -
20
Jandy is an internet development framework based on Indy, designed to make writing web clients and servers easier. Currently only the HTTP client and HTTP server frameworks are working, but other protocols will be included, like FTP, POP3, SMTP, etc.
-
21
Forwards non-NTLM HTTP client requests to an NTLM proxy server (ie. Microsoft IAS). Can also forward a local port to a remote machine.
-
22
NetCoreServer
Ultra fast and low latency asynchronous socket server & client C#
Ultra fast and low latency asynchronous socket server & client C# .NET Core library with support TCP, SSL, UDP, Unix Domain Socket, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution. Has an integration with high-level message protocol based on Fast Binary Encoding. Cross-platform (Linux, MacOS, Windows) Asynchronous communication. Supported transport protocols: TCP, SSL, UDP, UDP multicast, Unix Domain Socket. Supported Web protocols: HTTP, HTTPS, WebSocket, WebSocket secure. Supported Swagger OpenAPI iterative documentation. Supported message protocol based on Fast Binary Encoding. -
23
Netfox
A lightweight, one line setup, iOS / OSX network debugging library
Netfox provides a quick look on all executed network requests performed by your iOS or OSX app. It grabs all requests - of course yours, requests from 3rd party libraries (such as AFNetworking, Alamofire or else), UIWebViews, and more. -
24
The original intent was to make a pretty simple "connect and send" http client, it has since grown to include as much http 1.0 client capabilitlies (as defined in RFC 1945) as possible.
-
25
Requests for PHP
Requests for PHP is a humble HTTP request library
Requests is a HTTP library written in PHP, for human beings. It is roughly based on the API from the excellent Requests Python library. Requests is ISC Licensed (similar to the new BSD license) and has no dependencies, except for PHP 5.6+. Despite PHP’s use as a language for the web, its tools for sending HTTP requests are severely lacking. cURL has an interesting API, to say the least, and you can’t always rely on it being available. Sockets provide only low-level access and require you to build most of the HTTP response parsing yourself. Requests allows you to send HEAD, GET, POST, PUT, DELETE, and PATCH HTTP requests. You can add headers, form data, multipart files, and parameters with basic arrays, and access the response data in the same way. Requests uses cURL and fsockopen, depending on what your system has available, but abstracts all the nasty stuff out of your way, providing a consistent API.
