tls.connect fallback
Turn a function into an `http.Agent` instance
FTP client for Node.js, supports FTPS over TLS, IPv6, Async/Await, and Typescript.
A socket implementation that can run on Cloudflare Workers using native TCP connections.
MongoDB Shell CLI REPL Package
MongoDB Shell CLI REPL
Transport Layer Security (TLS) streams for JavaScript
A pure-JS module to read TLS client hello data and fingerprints from an incoming socket connection
A Pulumi package to create TLS resources in Pulumi programs.
Detects the ALPN protocol
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Process-global proxy routing for Node.js.
Easy as cake e-mail sending from your Node.js applications
NodeJS/browser bindings to the aws-c-* libraries
A port of the tls module for the browser.
OAuth 2.0 Authorization Server implementation for Node.js with OpenID Connect
Popsicle transport for sending requests over HTTP1 and HTTP2
React Native TCP socket API for Android & iOS with SSL/TLS support
Infinispan Javascript client
Node.js tls module for Gjs
TypeScript definitions for connect
Connects queues to Taskforce
A robust, performance-focused and full-featured Valkey/Redis client for Node.js.
jks-js is a converter of Java Key Store (JKS) to PEM certificates in order to securely connect to Java based servers using node js.
Command-line client for web sockets, like netcat/curl/socat for ws://.
Command-line client for web sockets, like netcat/curl/socat for ws://.
Reserved.
Connector similar to openssl or native-tls for rustls
Windows CertStore loader and ruby-openssl extension for TLS connection.
Checks negotiated TLS key exchange groups for RubyGems gem-server HTTPS connections.
Zokor is an HTTP proxy tunnelling tool that collapses multiple HTTP proxies into one. It's useful when you want to send traffic through a chain of two HTTP proxies where the first supports the CONNECT verb. Zokor presents a local server that transparently tunnels packets through the first proxy as though clients were directly connected to the second proxy. It optionally uses TLS to connect to the second proxy.
OverSIP is an async SIP proxy/server programmable in Ruby language. Some features of OverSIP are: - SIP transports: UDP, TCP, TLS and WebSocket. - Full IPv4 and IPv6 support. - RFC 3263: SIP DNS mechanism (NAPTR, SRV, A, AAAA) for failover and load balancing based on DNS. - RFC 5626: OverSIP is a perfect Outbound Edge Proxy, including an integrated STUN server. - Fully programmable in Ruby language (make SIP easy). - Fast and efficient: OverSIP core is coded in C language. OverSIP is build on top of EventMachine-LE async library which follows the Reactor Design Pattern, allowing thousands of concurrent connections and requests in a never-blocking fashion.
OverSIP is an async SIP proxy/server programmable in Ruby language. Some features of OverSIP are: - SIP transports: UDP, TCP, TLS and WebSocket. - Full IPv4 and IPv6 support. - RFC 3263: SIP DNS mechanism (NAPTR, SRV, A, AAAA) for failover and load balancing based on DNS. - RFC 5626: OverSIP is a perfect Outbound Edge Proxy, including an integrated STUN server. - Fully programmable in Ruby language (make SIP easy). - Fast and efficient: OverSIP core is coded in C language. OverSIP is build on top of EventMachine async library which follows the Reactor Design Pattern, allowing thousands of concurrent connections and requests in a never-blocking fashion.
Provides SMTP STARTTLS support for Ruby 1.8.6 (built-in for 1.8.7+). Simply require 'smtp_tls' and use the Net::SMTP#enable_starttls method to talk to servers that use STARTTLS. require 'net/smtp' begin require 'smtp_tls' rescue LoadError end smtp = Net::SMTP.new address, port smtp.enable_starttls smtp.start Socket.gethostname, user, password, authentication do |server| server.send_message message, from, to end You can also test your SMTP connection settings using mail_smtp_tls: $ date | ruby -Ilib bin/mail_smtp_tls smtp.example.com submission \ "your username" "your password" plain \ from@example.com to@example.com Using SMTP_TLS 1.0.3 -> "220 smtp.example.com ESMTP XXX\r\n" <- "EHLO you.example.com\r\n" -> "250-smtp.example.com at your service, [192.0.2.1]\r\n" -> "250-SIZE 35651584\r\n" -> "250-8BITMIME\r\n" -> "250-STARTTLS\r\n" -> "250-ENHANCEDSTATUSCODES\r\n" -> "250 PIPELINING\r\n" <- "STARTTLS\r\n" -> "220 2.0.0 Ready to start TLS\r\n" TLS connection started <- "EHLO you.example.com\r\n" -> "250-smtp.example.com at your service, [192.0.2.1]\r\n" -> "250-SIZE 35651584\r\n" -> "250-8BITMIME\r\n" -> "250-AUTH LOGIN PLAIN\r\n" -> "250-ENHANCEDSTATUSCODES\r\n" -> "250 PIPELINING\r\n" <- "AUTH PLAIN BASE64_STUFF_HERE\r\n" -> "235 2.7.0 Accepted\r\n" <- "MAIL FROM:<from@example.com>\r\n" -> "250 2.1.0 OK XXX\r\n" <- "RCPT TO:<to@example.com>\r\n" -> "250 2.1.5 OK XXX\r\n" <- "DATA\r\n" -> "354 Go ahead XXX\r\n" writing message from String wrote 91 bytes -> "250 2.0.0 OK 1247028988 XXX\r\n" <- "QUIT\r\n" -> "221 2.0.0 closing connection XXX\r\n" This will connect to smtp.example.com using the submission port (port 587) with a username and password of "your username" and "your password" and authenticate using plain-text auth (the submission port always uses SSL) then send the current date to to@example.com from from@example.com. Debug output from the connection will be printed on stderr.
Scrapetor is a Ruby HTML parsing + scraping toolkit. The parser is a native C arena DOM with structural indexes built at parse time and NEON SIMD scanners in the SAX hot loop. A streaming extraction engine compiles the schema DSL into a single forward pass — no DOM materialised, one Ruby boundary crossing per document. On builds where libcurl is available, Scrapetor::Fetcher adds an HTTP/2-capable fetch layer with per-thread connection cache, shared DNS + TLS session pool, in-process gzip / deflate / brotli / zstd decoding, iconv charset transcoding, retry + exponential backoff, ETag / Last-Modified disk cache with bulk revalidation, per-host throttle, cookie jar, basic + bearer auth, proxy, and three bulk concurrency models (parallel_fetch / multi_fetch / streaming multi_each). Scrapetor::Session ties the cookie / auth / throttle / retry policies together. Also ships robots.txt + sitemap.xml parsers, a bounded-memory streaming HTML parser, and structured-data extractors (JSON-LD, OpenGraph, Schema.org, Microdata, RDFa, Twitter Cards). The Net::HTTP-based Scrapetor.fetch is preserved as the no-libcurl fallback.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.