# HTTP Server Published articles for HTTP Server. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Workshop Basel day two DevFeed: [Workshop Basel day two]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-15T20:07:14Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [servers](), [Artificial Intelligence](), [Git](), [Open Source]() Tags: [ai](), [git](), [http](), [http-3](), [http-server](), [http-workshop](), [measurement](), [network](), [open-source](), [performance](), [quic](), [tests](), [web]() ### AI overview A report from the second day of a Basel workshop covering AI's influence on HTTP implementation, HTTP/2 measurements from large-scale web crawls, HTTP/1.1 behavior testing, request-smuggling tests, server performance measurement, and efforts to increase HTTP/3 and QUIC usage. ### Source excerpt If you missed it. I already described day one. Caffeinated and ready, we all gathered in the same spacious room as yesterday, but seated in new places as "suggested" by our captain. Some of us even remembered to move over the name tags we wrote yesterday to our new seats. No time was wasted on ... Continue reading Workshop Basel day two -> ## Rust smoltcp as an alternative TCP/IP stack for ESP-IDF DevFeed: [Rust smoltcp as an alternative TCP/IP stack for ESP-IDF]() Original publisher: [Read original article]() Author: John Lee Published: 2026-06-19T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Rust](), [networking](), [ESP32](), [ESP32-P4](), [HTTP](), [MQTT]() Tags: [blog](), [c](), [concurrency](), [esp-idf](), [esp32-p4](), [ethernet](), [firmware](), [http](), [http-server](), [ipv4](), [ipv6](), [lwip](), [mqtt](), [networking](), [rust](), [smoltcp](), [tcp-ip](), [tls]() ### AI overview This article explains how to run the Rust smoltcp TCP/IP stack as an alternative IPv4/IPv6 data plane under ESP-IDF. It describes a GNU linker --wrap shim that preserves compatibility with ESP-IDF networking components such as esp_http_server, esp-tls and esp-mqtt, along with the single-task poll architecture, measured ESP32-P4 throughput, and known limitations. ### Source excerpt A set of ESP-IDF components that run the Rust smoltcp stack as the IPv4/IPv6 data plane, while keeping esp_http_server, esp-tls and esp-mqtt working without source changes. This article explains the linker -wrap shim that makes it compatible, the single-task poll architecture, the throughput I measured on an ESP32-P4 (91.15 Mbit/s on a 100 Mbit link), and the limitations to be aware of. ## netlab 26.01: EVPN for VXLAN-over-IPv6, Netscaler DevFeed: [netlab 26.01: EVPN for VXLAN-over-IPv6, Netscaler]() Original publisher: [Read original article]() Published: 2026-01-13T06:19:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [releases](), [evpn](), [VXLAN](), [Ansible](), [Release notes](), [API](), [HTTP](), [Deployment]() Tags: [ansible](), [api](), [deployment](), [evpn](), [http](), [http-server](), [ipv6](), [netlab](), [release](), [release-notes](), [releases](), [vxlan]() ### AI overview netlab Release 26.01 rewrites device configuration file generation, removes its use of Ansible Jinja2 functionality, and supports Ansible releases 12 and 13 for configuration deployment. It also adds EVPN for VXLAN-over-IPv6, the skip_config node attribute, a lightweight API HTTP server, and rudimentary Citrix Netscaler support. ### Source excerpt I completely rewrote netlab's device configuration file generation during the New Year break. netlab Release 26.01 no longer uses Ansible Jinja2 functionality and works with Ansible releases 12/13, which are used solely for configuration deployment. I had to break a few eggs to get there; if you encounter any problems, please open an issue. Other new features include: EVPN for VXLAN-over-IPv6 The 'skip_config' node attribute that can be used to deploy partially-provisioned labs Lightweight netlab API HTTP server by Craig Johnson Rudimentary support for Citrix Netscaler by Seb d'Argoeuves You'll find more details (and goodies) in the release notes. Read more ... ## ESP-IDF Tutorials: Basic HTTP server DevFeed: [ESP-IDF Tutorials: Basic HTTP server]() Original publisher: [Read original article]() Author: John Lee Published: 2025-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [HTTP](), [Espressif](), [servers](), [HTML](), [CMake](), [browser]() Tags: [article](), [blog](), [browser](), [cmake](), [devices](), [esp](), [esp-idf](), [espressif](), [html](), [http-server](), [practitioner](), [tutorial](), [tutorials]() ### AI overview This tutorial explains how to set up a basic HTTP server with ESP-IDF, create a URI route that serves an HTML page, and view that page in a web browser on Espressif devices. ### Source excerpt This article shows how to create a simple HTTP server. It explains the functions you need and the setup required. After reading this, you should be able to create your own HTTP server on Espressif devices. ## ESP-IDF Tutorials: Soft-AP DevFeed: [ESP-IDF Tutorials: Soft-AP]() Original publisher: [Read original article]() Author: John Lee Published: 2025-04-18T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Espressif](), [Tutorial](), [networking](), [configuration]() Tags: [blog](), [bluetooth](), [bluetooth-le](), [configuration](), [connectivity](), [esp-idf](), [esp32-c3](), [espressif](), [framework](), [http](), [http-server](), [networking](), [security](), [soft-ap](), [tutorials](), [wi-fi]() ### AI overview This tutorial explains how to set up a Wi-Fi soft-AP with an Espressif module and ESP-IDF for provisioning. It covers project setup, Wi-Fi configuration, event handling, and verifying the connection with a smartphone, while noting that the simple technique is less secure than Unified Provisioning. ### Source excerpt This tutorial guides you through setting up a soft-AP using an Espressif module and ESP-IDF. It covers the process of creating a project, configuring Wi-Fi, and handling connection events through event loops. Upon completion, you'll be able to establish a soft-AP and manage Wi-Fi connections. It is the first step to building more advanced networking applications. ## Multi-function USB Dongle based on ESP32-S3 DevFeed: [Multi-function USB Dongle based on ESP32-S3]() Original publisher: [Read original article]() Author: John Lee Published: 2024-10-24T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-S3](), [USB](), [Data Management]() Tags: [blog](), [dongle](), [esp32-s3](), [espressif](), [http-server](), [usb]() ### AI overview The article presents a multi-function USB dongle based on the Espressif ESP32-S3 module. It addresses cumbersome workflows for transferring camera photos, printing files, and sharing videos, and describes a device combining a USB MSC wireless disk with a USB wireless network card and dual-function switching. ### Source excerpt In modern digital life, we often encounter scenarios where data transfer is not flexible or efficient enough, especially when exporting camera photos, printing files, and sharing videos. In this article, we will have a closer look at the mentioned scenarios and propose a solution - Multi-function USB Dongle based on ESP32-S3. ## Ep. 5: Efficient Concurrency in Go: Managing GoRoutines and Load Shedding DevFeed: [Ep. 5: Efficient Concurrency in Go: Managing GoRoutines and Load Shedding]() Original publisher: [Read original article]() Published: 2024-06-11T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Concurrency](), [Go Language](), [Concurrent Programming](), [HTTP](), [servers]() Tags: [best-practices](), [concurrency](), [go](), [goroutines](), [http](), [http-server](), [kubernetes-clusters](), [load](), [managing-goroutines](), [networking](), [programming](), [server]() ### AI overview This video tutorial explains how to manage goroutines in Go using parent-child relationships, clean shutdown APIs, and load shedding. It focuses on preventing orphaned goroutines, protecting data consistency during shutdowns, and gracefully handling HTTP server traffic. ### Source excerpt Introduction: In this installment, Bill delves into the concept of load shedding in Go, explaining its importance in managing GoRoutines and ensuring clean shutdowns. How to manage GoRoutines using a parent-child relationship model to prevent orphan GoRoutines. The role of load shedding in maintaining clean and orderly shutdowns, particularly using the HTTP package in Go. Strategies for implementing GoRoutines in Go to handle concurrent tasks efficiently without risking data corruption during shutdowns. ## Exploiting HTTP/2 CONTINUATION frames for DoS attacks DevFeed: [Exploiting HTTP/2 CONTINUATION frames for DoS attacks]() Original publisher: [Read original article]() Author: Vandana Verma Sehgal Published: 2024-04-08T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [HTTP](), [vulnerability](), [DDoS](), [servers](), [web applications](), [Go Language](), [Node.js]() Tags: [attacks](), [awareness](), [blog](), [code-security](), [developer](), [devops](), [devrel](), [enablement](), [engineering](), [go](), [http](), [http-server](), [internet-traffic](), [js](), [monitor](), [node-js](), [open-source-security](), [performance](), [security](), [server](), [snyk-open-source](), [snyk-platform](), [vulnerability](), [vulnerability-insights]() ### AI overview This article explains a vulnerability in HTTP/2 implementations that lets attackers flood a single stream with excessive CONTINUATION frames, potentially overwhelming or crashing web servers. It describes the affected ecosystem, including Node.js and Go, and recommends patching, rate limiting, traffic monitoring, and temporarily disabling HTTP/2 when no patch is available. ### Source excerpt This post covers all the info you need on the new HTTP/2 CONTINUATION frames vulnerability, including the affected versions, its impact, mitigation steps, and how to protect your applications. ## Router 2.0 Common Runtime Router: The Road to Beta DevFeed: [Router 2.0 Common Runtime Router: The Road to Beta]() Original publisher: [Read original article]() Author: Elizabeth Cox Published: 2023-10-30T22:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Routing (disambiguation)](), [Erlang](), [servers](), [Concurrency](), [legacy](), [Scalability](), [Open Source]() Tags: [concurrency](), [engineering](), [erlang](), [http-server](), [legacy](), [modernization](), [open-source](), [release](), [router-2-0](), [routing](), [scalability]() ### AI overview Heroku describes the beta release of Router 2.0, a replacement for the existing Common Runtime router planned for 2024. The article explains the legacy router's Erlang-based architecture and the challenges that motivated a new implementation, including safer delivery of routing features and planned HTTP/2 support. ### Source excerpt Last month, Heroku announced the beta release of Router 2.0, the new Common Runtime router! As part of our commitment to infrastructure modernization, Heroku is making upgrades to the Common Runtime routing layer. The beta release of Router 2.0 is an important step along this journey. We're excited to give you an inside look at [...] The post Router 2.0 Common Runtime Router: The Road to Beta appeared first on Heroku. ## Interfaces 101 : Extensible API Handlers Ep. 10 DevFeed: [Interfaces 101 : Extensible API Handlers Ep. 10]() Original publisher: [Read original article]() Published: 2023-04-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [HTTP](), [Server](), [Logging](), [interfaces]() Tags: [api](), [go](), [golang](), [handler](), [http](), [http-server](), [interfaces](), [logging](), [middleware](), [request](), [web]() ### AI overview A video tutorial demonstrates how to build an extensible HTTP API handler in Go. It covers defining a route and handler, designing composable middleware, and implementing logging middleware that measures request time. ### Source excerpt Introduction In episode 9, Miki discussed how a command flag can be decoded into a user defined type with the Value interface. As a recap, the Value interface consists of two methods: one for serializing the underlying concrete type and one for deserializing a string into an object. To put this interface to the test, Miki wrote a command that had a flag to specify a network address. While implementing the Set method of the Value interface, Miki demonstrated how to add validation for your program's flags. ## Open Sourcing Intervene DevFeed: [Open Sourcing Intervene]() Original publisher: [Read original article]() Published: 2020-05-05T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Intervene](), [Mocking](), [TypeScript](), [BFF](), [Web](), [Processes](), [browser](), [JavaScript](), [API]() Tags: [api](), [bff](), [browser](), [code](), [configuration](), [dev-tools](), [documentation](), [frontend](), [http](), [http-server](), [intervene](), [javascript](), [mocking](), [node-js](), [open](), [process](), [proxy](), [tools](), [typescript](), [web](), [web-development]() ### AI overview SoundCloud open-sources Intervene, a Node.js process that acts as a single-host proxy for altering requests and responses during frontend development. It supports endpoint overrides, TypeScript or JavaScript configuration, automatically trusted self-signed HTTPS certificates, and repository-shared mocks. ### Source excerpt A little while back, the web team at SoundCloud got an urgent report that our upload page looked weird in the US. Web engineering is based... ## HTTP 555: User-Defined Resource Error DevFeed: [HTTP 555: User-Defined Resource Error]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2020-03-27T13:30:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [HTTP](), [Protocol (disambiguation)](), [Serverless]() Tags: [errors](), [http](), [http-server](), [protocol](), [serverless](), [standards]() ### AI overview The article examines Oracle's proposed HTTP status code 555 for server-side errors caused by user-supplied resources in serverless systems. It explains HTTP status-code categories and emphasizes that the proposal is not standardized and should not be used in production. ### Source excerpt Does the rise of serverless mean we need a new HTTP status code? The team at Oracle think so. They've submitted a draft specification to the HTTP Working Group, defining a new HTTP status code (initially suggesting 555) to be used for server-side errors caused by user-supplied resources. [Note: I'm going to use 555 to refer to the new proposed code everywhere here, but this is not standardized, even if it is standardized in future it will probably use a different code, and you 100% should not start building anything that uses this code for real anywhere. Nobody needs another 418 I'm A Teapot battle.] Anyway, let's talk about what this means, and whether it's a good idea. Status codes: a refresher First let's recap the background. Status codes are 3 digit codes, included in every response from an HTTP server, which summarize the result of a request. There's common examples you'll have heard of like 404 (the resource you requested could not be found) or 200 (your request was successful, and this response represents the result). There's then a long list of less common examples, like 302 (the resource you requested is a temporarily stored elsewhere, you should go there instead), 410 (the resource you requested was here, but now it's gone, and there's no new address available), or 100 (yes, please continue sending the rest of the request you're already sending). And many more. They're categorized into a few classes: 1XX: Information These are provisional responses, which typically don't fit into the simple HTTP request/response flow, and describe unusual behaviors like interim responses or switching the connection to a different protocol. 2XX: Success The request you asked for was successful in some way. Perhaps you're getting the resource you asked for (200), the server has accepted and started asynchronously processing your operation (202), or your request was successful but the server doesn't have any data about it for you (204). 3XX: Redirection Your request is valid ## Local Network Access via HTTP Server DevFeed: [Local Network Access via HTTP Server]() Original publisher: [Read original article]() Author: John Lee Published: 2018-10-13T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [HTTP](), [servers](), [API](), [Networks](), [Wi-Fi](), [Security]() Tags: [api](), [blog](), [building-products](), [code](), [curl](), [esp32](), [http](), [http-server](), [network](), [security](), [wi-fi](), [wifi]() ### AI overview This tutorial explains how to let a smart device on a user's home network expose a /power HTTP URI. GET reports the device's current output state, while POST updates it. It also shows registering handlers, testing with cURL, using a phone app, and the security implications of relying on Wi-Fi protection. ### Source excerpt So you have your smart device on your end-user's home network. Now you would want your user to access your device over the local network. That's what we will look at in this post. Let's say you are building a smart plug, and you want to toggle the power on or off on your plug. We will create a HTTP URI */power *on your device. - An HTTP GET on this URI will give us the current state of the output of the plug. - An HTTP POST on this URI will update the output state of the plug. ## How to pass variables to a Docker container when building a Node app DevFeed: [How to pass variables to a Docker container when building a Node app]() Original publisher: [Read original article]() Author: Federico Published: 2016-11-05T21:42:00Z Content type: tutorial Language: en Sources: [Federico Cargnelutti]() Topics: [Dockerfile](), [Environment Variables](), [Docker Image](), [Command-line interface]() Tags: [command-line](), [docker](), [docker-image](), [environment-variables](), [http-server](), [javascript](), [linux](), [node-js](), [npm](), [open-source](), [port](), [programming]() ### AI overview A tutorial on passing variables to a Dockerized Node application during image builds and container execution. It explains Dockerfile ENV and ARG instructions, command-line build arguments, shell-based use of NODE_ENV, and exposing a port to start an HTTP server. ### Source excerpt Environment variables are declared with the ENV statement and are notated in the Dockerfile either with $VARIABLE_NAME or ${VARIABLE_NAME}. Passing variables at build-time The ENV instruction sets the environment variable to the value. The environment variables set using ENV will persist when a container is run from the resulting image. For example: The Dockerfile allows you to specify arguments [...] ## Weekly Programming Challenge #10 DevFeed: [Weekly Programming Challenge #10]() Original publisher: [Read original article]() Author: Jamis Published: 2016-10-01T06:00:00Z Content type: tutorial Language: en Sources: [Jamis Buck]() Topics: [Programming](), [Network](), [Server](), [client](), [HTTP](), [Ruby]() Tags: [code](), [elixir](), [http](), [http-server](), [javascript](), [network](), [programming](), [server]() ### AI overview This article introduces a weekly programming challenge focused on socket programming. It asks readers to explore writing a simple client and server that exchange information over a network, after recapping submissions for the previous challenge on Bezier curves. ### Source excerpt Socket programming -- 5-minute read ## Preparing a Web Front Server for DoS Attacks Using Cloudflare-Inspired Techniques DevFeed: [Preparing a Web Front Server for DoS Attacks Using Cloudflare-Inspired Techniques]() Original publisher: [Read original article]() Author: Tom Published: 2016-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [DDoS](), [Cloudflare](), [conntrack](), [Kernel](), [servers]() Tags: [cloudflare](), [conntrack](), [ddos](), [http-server](), [kernel](), [performance](), [security]() ### AI overview This tutorial adapts general techniques from a presentation about Cloudflare's DoS protection for typical web front servers. It covers ACK/FIN/RST/X-mas floods, SYN floods, botnet attacks, conntrack, syncookies, rate limiting, IP blacklisting, and related kernel and network tuning. ### Source excerpt I watched nice presentation about how Cloudflare protects itself against DoS. Most of us are not able to do that exactly like them but some of tips were general enough to be used on typical web front server. I took notes from this presentation and presented here. Thanks to Marek agreement I also reposted all examples (in easier to copy paste way). Howto prepare against ACK/FIN/RST/X-mas flood Use conntrack rule: ## Cat-DNS: a DNS server that resolves everything to cats DevFeed: [Cat-DNS: a DNS server that resolves everything to cats]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2014-02-18T00:00:00Z Content type: tutorial Language: en Sources: [Monica Dinculescu]() Topics: [HTTP](), [servers](), [Internet](), [Code](), [web applications]() Tags: [client](), [dns](), [http](), [http-server](), [localhost](), [server](), [udp](), [website]() ### AI overview A playful tutorial for running Cat-DNS, a Node-based DNS server that resolves hostnames to a fixed cat-hosting IP address. It explains running the server on UDP port 53, configuring localhost as the DNS server, and switching the configuration back when finished. ### Source excerpt The internet needs more cats. DNS servers are the authority on all things internet. Therefore, the best DNS server is the one that resolves everything to cats. Guess what kind of DNS server this is (Hint: it's the cat kind). Making it go First, get the code, and the npm packages you need (the instructions are with the code). To run, start the server as a privileged process. This is because to be a DNS server, you need to be a UDP server on port 53. This is a small numbered port, which means it needs superpowers. This is how your run it: sudo node cat-dns.js You also need to somehow set your DNS server to be localhost. On a Mac, I do this by creating a new (wi-fi) interface (called Cats), in my Network preferences, and setting its DNS server to 127.0.0.1. You could do this on your normal interface, but this makes switching back and forth easier. Warnings While you're playing with this, pretty much nothing on your computer that requires the internet works. Except for your browser. And then that's mostly cats. So being able to deactivate this easily is kind of key (I know. You might think "Why would I ever want to deactivate cats?", but trust me on this one). I also recommend killing all the things that need to call the mothership (google hangouts, twitter feeds, dropbox, iMessage), because they will not like your sassy cat answers, and will slow everything down. You are ready Go in your browser to www.google.com and wait a bit. You should see a cat. Go to a different website. Another cat. Congratulations. Your internet is now all cats. Wait, what? Do not panic. While I recommend you don't look at the source because it's gross, if you do look at the source, you'll notice all it does is resolve any hostname to 54.197.244.191, which is a magical place on the internet that has cats. My friend @eigma made it, and is hosting it, so please try not to kill all the cat bandwith at once. You could also resolve everything to localhost, and serve your own for now cats on an http