HTTP on Support Tools

Go's ServeMux Evolution: HTTP Routing in Go 1.22 and Beyond

Thu, 23 Jul 2026 09:00:00 -0500

Go 1.22 introduced significant enhancements to the standard library’s HTTP router, ServeMux. These improvements bring the built-in router closer to feature parity with many third-party HTTP routers, potentially eliminating the need for external dependencies in many web applications.

Building a High-Performance HTTP Router in Go from Scratch

Thu, 09 Oct 2025 09:00:00 -0500

HTTP routers are fundamental components of web applications, directing incoming requests to the appropriate handlers. While Go’s standard library provides a basic router with http.ServeMux, building your own gives you deeper insights into web internals and allows for custom routing capabilities. This guide walks through implementing a high-performance HTTP router from scratch.

Benchmarking and Optimizing Go HTTP Routers: Performance Strategies

Thu, 02 Oct 2025 09:00:00 -0500

HTTP routers form the backbone of web applications, determining how quickly incoming requests are directed to appropriate handlers. As applications scale, router performance becomes increasingly critical. This guide explores strategies for benchmarking and optimizing HTTP routers in Go, with practical techniques to squeeze out maximum throughput and minimize latency.

Running Apache with mod_spdy and PHP-FPM: Performance Optimization Guide

Tue, 30 Sep 2025 09:00:00 -0600

Master the art of high-performance web serving by combining Apache’s mod_spdy with PHP-FPM for optimal speed and resource utilization.

Benchmarking Go HTTP Routers: Performance Comparison and Analysis

Tue, 23 Sep 2025 09:00:00 -0500

When building web applications or APIs in Go, choosing the right HTTP router can significantly impact performance, especially at scale. This article analyzes and compares the performance characteristics of popular Go HTTP routers to help you make an informed choice for your next project.

Varnish Cache Tuning: VCL, Grace, Bans and Hit Rate

Sun, 25 May 2025 16:34:42 -0500

Varnish ships with a built-in VCL that is deliberately conservative: any request with a Cookie or Authorization header goes straight to the backend, and any response with Set-Cookie is not cached. On a real site, where every browser sends analytics cookies, that means the cache does almost nothing. This guide covers the VCL changes that actually move the hit rate, how to keep serving during backend outages, how to invalidate content safely, how to size storage, and how to prove each change with varnishstat and varnishlog.

Advanced Linux Web Server Programming: Building High-Performance HTTP Servers and Web Applications

Sun, 20 Apr 2025 10:00:00 -0500

Advanced Linux web server programming requires deep understanding of network programming, async I/O, and high-performance server architectures. This comprehensive guide explores building custom HTTP servers using epoll, implementing WebSocket support, SSL/TLS integration, and creating scalable web applications that can handle thousands of concurrent connections.

cURL Host Header: Set It With -H, --resolve or --connect-to

Mon, 25 Nov 2024 23:00:00 -0500

Setting the HTTP Host header with cURL is how you test a virtual host, a load balancer or a new server before you change DNS. This guide gives the exact commands for HTTP and HTTPS, explains why -H 'Host: ...' alone fails on HTTPS, and ends with a small hcurl shell helper so you never have to look the syntax up again.

Change Default HTTP Port for Bitnami/nginx Web Server Using ConfigMap in Kubernetes

Sat, 12 Oct 2024 19:26:00 -0500

When running a Bitnami/nginx web server in Kubernetes, you might need to change the default HTTP port (which is typically port 80) to a different port for various reasons, such as security policies, port conflicts, or custom routing requirements. In this post, we’ll show you how to modify the default port of an NGINX web server using a ConfigMap in Kubernetes.

Change Default Ingress Port to HTTP for Bitnami/nginx in Kubernetes

Fri, 11 Oct 2024 19:26:00 -0500

When setting up Bitnami/nginx as your Ingress controller in a Kubernetes environment, the default configuration may use HTTPS (port 443). However, there are cases where you might want to change the default Ingress port to HTTP (port 80), especially if you’re dealing with non-HTTPS traffic or need to expose services through standard HTTP.

In this post, we will walk through how to modify the default Ingress port for Bitnami/nginx in Kubernetes to use HTTP (port 80) instead of HTTPS, allowing you to handle non-encrypted traffic effectively.