Skip to main content
100%

Gist 4985631

✓ Published0🌍 Public
Aalessioalex
Last edited Oct 10, 2012
Created on Feb 19, 2013

This example demonstrates how to configure a Node.js HTTPS server with Server Name Indication (SNI) to serve multiple SSL certificates for different hostnames. It shows the setup for routing requests to distinct backend ports using the http-proxy library, with an SNICallback that selects the appropriate certificate context based on the incoming hostname. The code uses Node.js core `crypto.createCredentials` and `fs.readFileSync`, along with a custom `getCABundle` function that parses a bundled certificate file into an array by splitting on the `-END CERTIFICATE-` marker. It explicitly maps example-a.com and example-b.com to localhost ports 10000 and 10001.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 4985633

This example demonstrates a multi-domain HTTP/HTTPS reverse proxy server built with Node.js and the `http-proxy` module. It routes incoming requests to distinct backend applications based on the requested hostname, with separate configurations for `www1.localhost` and `www2.localhost`. The server uses `crypto.createCredentials` for HTTPS SNI callbacks, enabling per-domain TLS certificates. Each backend app, defined in separate files like `www1_app.js`, responds with a plain-text message confirming the successful proxy and echoing request headers, illustrating how the proxy handles both HTTP and HTTPS traffic across multiple virtual hosts.

Aalessioalex
82% match
Loading thumbnail…

Gist 4698533

This example implements a SOCKS5 proxy server in Node.js, demonstrating the TCP connection flow between a client, proxy, and destination. It shows the handshake, authentication (using USERPASS), and request forwarding stages. The code uses the `net` module’s `createServer` and `createConnection` APIs to handle incoming sockets and outbound TCP links, with buffer manipulation for parsing SOCKS5 headers, address types (IPv4, domain, IPv6), and ports. All connections are accepted, authorized, and relayed, though the `authorize` function always returns true.

Aalessioalex
66% match
Loading thumbnail…

Gist 6fc452a19facae4857d0

This example demonstrates the process of setting up mutual TLS (client-side SSL) authentication for web servers. It walks through generating self-signed certificates using the OpenSSL command-line tool, including creating a Certificate Authority root, client keys, and PKCS#12 or PEM conversions for browser and application use. The guide references nginx configuration directives such as `ssl_client_certificate` and `ssl_verify_client` to request and validate client certificates, and it links to external resources for integrating with backend applications. The gist is a textual reference, not a data visualization.

ZZJONSSON
63% match
Loading thumbnail…

Use https certificate on localhost with Express

This example shows how to run an Express web server over HTTPS on localhost, delivering a plain-text response. It creates a Node.js application that reads SSL certificate files (`localhost-key.pem` and `localhost.pem`) generated by the mkcert utility, then uses the `https.createServer` method with those credentials. The Express app defines a single route for the root path, and the server listens on port 3001. The code demonstrates the required setup steps, including installing mkcert and generating a trusted local certificate.

TThomasG77
62% match
Loading thumbnail…

http-debugging-proxy.js

This example demonstrates a custom HTTP proxy server that intercepts requests and serves local files or forwards traffic to a remote target. The code uses Node.js’s `http` module and the `http-proxy` library to create a server listening on port 5050. It checks the request URL for specific paths like `/package/http-proxy` or `/local.css` to stream local HTML or CSS files via `fs.createReadStream`. All other requests are proxied to `https://www.npmjs.org` using `proxy.web(req, res, { target })`, showing conditional routing and file serving alongside proxying.

Aalessioalex
62% match
Loading thumbnail…

Title :: LetsEncrypt.md

This example shows how to configure HTTPS certificates from Let's Encrypt across three server environments. The code demonstrates obtaining certificates via the `letsencrypt-auto` command-line tool with the `certonly --manual` flag, which requires placing a verification file on the domain. The Node.js implementation uses the `https` module with `fs.readFileSync` to load the PEM files from `/etc/letsencrypt/live/example.com/`. The Apache configuration uses `SSLCertificateFile`, `SSLCertificateKeyFile`, and `SSLCertificateChainFile` directives, while the NGINX setup relies on `ssl_certificate` and `ssl_certificate_key` directives pointing to `fullchain.pem` and `privkey.pem`.

Aaniston
61% match
Loading thumbnail…

Gist 5383090

This example shows how to forward external HTTP traffic from port 80 to an internal Node.js server listening on port 8000 using iptables NAT rules. The text documents the command-line workflow, including listing the current NAT table, adding a PREROUTING redirect rule, and deleting faulty rules by chain and line number. It also warns against running Node as root for security reasons and acknowledges the risk of disrupting SSH access on port 22. No visualization code or data is present; the example is purely textual documentation of a system administration procedure.

Aalessioalex
61% match
Loading thumbnail…

Gist 884836

This visualization demonstrates an nginx configuration for proxying requests to a Node.js application running on port 8001. It shows the setup of an upstream server group named "node" and a server block listening on port 80, with access logging enabled. The code specifies root directory paths and includes fastcgi parameters while using proxy_pass to forward requests to the upstream. The example relies on nginx’s built-in HTTP proxy and FastCGI modules, with no external JavaScript libraries or rendering APIs involved.

Aalessioalex
60% match