# request Published articles for request. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Khan Academy Uses Local Storage and Request Queues to Handle Offline Actions DevFeed: [Khan Academy Uses Local Storage and Request Queues to Handle Offline Actions]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-08-17T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [LocalStorage](), [client](), [Code](), [Internet](), [servers]() Tags: [architecture](), [change](), [code](), [engineering](), [function](), [hints](), [linear](), [local](), [news](), [offline](), [queue](), [request](), [server](), [web-frontend]() ### AI overview This article explains how Khan Academy addressed offline hint cheating by changing the client's request architecture. Actions are stored in local storage and placed in a queue for retry when connectivity returns, with linear backoff to avoid repeated requests during outages. ### Source excerpt By Phillip Lemons The problem Recently, a number of students on Khan Academy found a way to cheat ... Read more ## MCP went stateless: What changed in the 2026-07-28 spec DevFeed: [MCP went stateless: What changed in the 2026-07-28 spec]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [migration](), [HTTP](), [servers](), [client]() Tags: [api](), [client](), [http](), [load-balancer](), [mcp](), [replacement](), [request](), [routing](), [server](), [servers](), [sessions](), [stateless](), [stream]() ### AI overview The 2026-07-28 MCP specification removes protocol-level sessions, the initialize handshake, and stream resumability, making the protocol behave more like an ordinary HTTP API. Most migrations are mechanical, but lost stream requests can cause reliability regressions or duplicated side effects when retried, so side-effecting tools need application-level idempotency keys. The elicitation change also requires architectural rework. ### Source excerpt Sessions, the initialize handshake, and stream resumability are all gone. Here is what replaced them, and what breaks if you ignore it. ## Linux server performance: Is disk I/O slowing your application? DevFeed: [Linux server performance: Is disk I/O slowing your application?]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-12T16:11:54Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [IO](), [Server](), [Command-line interface](), [Processes](), [NVMe]() Tags: [blog](), [command-line](), [cpu](), [linux](), [load](), [mysql](), [nvme](), [performance](), [processes](), [request](), [server](), [ssd](), [storage](), [sysadmins](), [terminal]() ### AI overview This tutorial explains how disk I/O bottlenecks can cause high Linux load averages even when CPU usage is low. It shows how to use top, atop, and iotop on a LEMP web server, including per-core I/O wait measurements, to identify storage-related application slowdowns. ### Source excerpt If your Linux server is bogged down by disk I/O, your first step may often be to use the top command in the terminal to check load averages. Continue reading... ## Introducing IP Allowlisting DevFeed: [Introducing IP Allowlisting]() Original publisher: [Read original article]() Author: Postmark team (fdossetto+postmark@activecampaign.com) Published: 2026-09-08T17:37:00Z Content type: release Language: en Sources: [Postmark (en-US)]() Topics: [Security](), [API](), [Network](), [Cloud]() Tags: [api](), [infrastructure](), [ip](), [nat](), [network](), [product-news](), [protection](), [range](), [request](), [security](), [token]() ### AI overview Postmark introduces IP Allowlisting, a security feature that restricts email sending through the Postmark API to up to 10 configured IP ranges in CIDR format. Requests from outside the allowed ranges are rejected with a 403 response. The ranges can be configured at the Server or account level, with Server settings overriding account settings. ### Source excerpt Good security is layered and each layer does a job the others can't. Scoping a token to a Server limits what it reaches. Rotating a token limits how long it lasts. Neither can say anything about where a request came from. We've been hard at work to ship a new layer of protection that can. IP Allowlisting is a new Postmark security feature that lets you name the infrastructure your email should come from. It's available now on all Postmark plans at no extra cost. It's off until you turn it on. How IP Allowlisting works You add up to 10 IP ranges, in CIDR format, that are allowed to send email using the Postmark API. Send requests from outside those ranges are rejected with a 403 status code that includes the IP the request came from. You can set your ranges in two places: On a Server. The ranges apply to that Server, covering every Message Stream on it. This is where we'd suggest starting. On your account. The ranges apply to every Server you have. When a Server has ranges of its own they will override account level settings. That's it! A straightforward security control to protect your API sending. Protect individual Servers or across your account. Set your Allowlist ranges on the account or Server. If you don't write CIDR blocks often, it's a quick 30 seconds to get familiar with them and the correct notation. CIDR blocks allow you to enable a grouped collection of IP addresses (aka ranges.) A CIDR block is an IP address followed by a suffix that says how many addresses it covers. The smaller the suffix, the wider the range: 198.51.100.24/32 one address, and only that address 203.0.113.0/24 256 addresses: 203.0.113.0 through 203.0.113.255 203.0.0.0/16 65,536 addresses: 203.0.0.0 through 203.0.255.255 So a /32 pins the allowlist to a single machine, and a /24 covers a subnet. Most teams end up somewhere in that span. Where you find your own ranges depends on how you send. A single VM has a static public IP you can read off your provider's dashboard. Cloud workloads ## The Evolution of HTTP, Clearly Explained DevFeed: [The Evolution of HTTP, Clearly Explained]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-04T16:39:02Z Content type: article Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [HTTP](), [client](), [servers](), [Caching](), [Web]() Tags: [browser](), [caching](), [encoding](), [evolution](), [http](), [http-3](), [protocol](), [request](), [responses](), [server](), [tcp]() ### AI overview An explanatory article traces HTTP from versions 0.9 through 1.1, describing how headers, status codes, persistent connections, caching, and chunked transfer encoding addressed the web's growing scale and performance needs. It introduces HTTP/3 as part of that broader evolution. ### Source excerpt From 0.9 to 3.0: What changed and why? ## Track LLM API Costs with genai-prices DevFeed: [Track LLM API Costs with genai-prices]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-09-01T11:16:32Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Large Language Model](), [API](), [Inference](), [Library](), [Python](), [Binance]() Tags: [api](), [cost](), [example](), [genai](), [inference](), [install](), [library](), [llm](), [openai](), [pricing](), [python](), [report](), [request](), [tips](), [token](), [uv]() ### AI overview A tutorial introducing the genai-prices Python library for estimating the cost of calling LLM inference APIs. It explains that the library can avoid maintaining a custom pricing table and can report token counts and cost for each request, with an OpenAI installation and usage example. ### Source excerpt Tip: Use the genai-prices Python library to calculate the estimated cost of calling LLM inference APIs. This avoids maintaining your own pricing table and lets you report token counts and cost for each request. Below is an example: # Install: uv add openai genai-prices from openai import OpenAI from ## How to Confirm Phone Number Ownership with Lookup Identity Match DevFeed: [How to Confirm Phone Number Ownership with Lookup Identity Match]() Original publisher: [Read original article]() Author: Kelley Robinson Published: 2026-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [API](), [Code](), [Command-line interface](), [Serverless](), [JavaScript]() Tags: [api](), [cli](), [code](), [developer-insights](), [fake-accounts](), [fraud](), [how-to](), [javascript](), [reduce](), [request](), [serverless](), [verify]() ### AI overview This tutorial explains how to use Twilio Lookup Identity Match to confirm that a person is linked to a phone number. It covers matching submitted identity details against authoritative data, setting up a JavaScript project with the Twilio CLI and Serverless plugin, and using the result to reduce sign-up fraud. ### Source excerpt Send details like name, address, or date of birth and the Identity Match API will tell you if they match a provided phone number. Reduce fraud and verify identities quickly. ## 【etcd】单 Raft 组与服务器角色：Leader、Follower、Learner 与 request 路由 DevFeed: [【etcd】单 Raft 组与服务器角色：Leader、Follower、Learner 与 request 路由]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [gRPC]() Tags: [apiserver](), [apply](), [atomic](), [commit](), [compaction](), [distributed](), [etcd](), [etcdserver](), [follower](), [kubernetes](), [leader](), [learner](), [linearizable](), [raft](), [request](), [single-raft-group](), [v3](), [v3-5](), [v3-5-33](), [wal](), [watch]() ### AI overview This article explains how etcd v3.5.33 embeds a single Raft group, separates EtcdServer responsibilities from the Raft library, and routes requests across Leader, Follower, and Learner roles. It covers gRPC write forwarding, linearizable and serializable reads, and the handling of watch, lease, and mutating requests. ### Source excerpt 钉清 etcd v3.5.33 单 Raft 组拓扑、EtcdServer 与 go.etcd.io/raft/v3 边界、Leader/Follower/Learner 角色及 gRPC 写读路由；与 distributed/13 分工。 ## Why GitHub feels less reliable lately DevFeed: [Why GitHub feels less reliable lately]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-23T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [GitHub](), [incident](), [migration](), [systems](), [Azure](), [GitHub Actions](), [pull-requests]() Tags: [autoscaling](), [capacity](), [concurrency](), [data-centers](), [deployment](), [github](), [incident](), [incident-management](), [istio](), [reliability](), [request](), [resilience](), [sre](), [transformation]() ### AI overview The article argues that GitHub's recent reliability problems reflect the difficult middle of a major infrastructure transformation. It connects incidents to migration complexity, unsafe automation, configuration mistakes, capacity and concurrency weaknesses, database migration errors, and autoscaling problems. ### Source excerpt GitHub is not having one outage problem. Its recent incident reports show the difficult middle of a platform transformation. ## How ORM N+1 Queries Create Hidden Request Latency DevFeed: [How ORM N+1 Queries Create Hidden Request Latency]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Object-relational mapping](), [Latency](), [Monitoring](), [lazy loading](), [Database](), [connection pool]() Tags: [connection-pool](), [database](), [database-performance](), [hibernate](), [latency](), [lazy-loading](), [monitoring](), [n-plus-one](), [observability](), [orm](), [query](), [request]() ### AI overview This article explains how ORM lazy loading can turn a loop over orders into an N+1 query pattern. Individual queries may remain fast and avoid slow-query alerts, while the accumulated network round trips increase request latency and hold connection-pool resources. It recommends monitoring queries per request and asserting query counts in tests. ### Source excerpt N+1 queries hide from monitoring because no individual query is slow. Four hundred queries at 0.4ms each never appear in the slow query log, never move p99 query latency, and still cost the request 300ms because the expense is the round trip rather than the execution. The metric that catches it is queries per request, and the only durable fix is asserting on that count in tests, since the code that causes it looks like a field access rather than I/O. ## Self-service peering with a PeeringDB login DevFeed: [Self-service peering with a PeeringDB login]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-07-27T00:00:00Z Content type: opinion Language: en Sources: [AS215248 - Notes]() Topics: [Networks](), [OAuth](), [Server]() Tags: [automation](), [bgp](), [dashboard](), [ipv4](), [ipv6](), [ixp](), [login](), [mail](), [networks](), [oauth](), [peering](), [permission](), [request](), [self-service]() ### AI overview The article describes a self-service peering portal that uses PeeringDB OAuth to authenticate users, verify ASN update rights, and offer exchanges where both networks are present. Requests create disabled sessions for manual approval, with inherited filtering and validation policies, notifications, and approval-based removal. ### Source excerpt Peering requests used to be mail ping-pong. Now you log in with PeeringDB on the peering page, pick an exchange, and the session is waiting for my approval. ## Workshop Basel day three DevFeed: [Workshop Basel day three]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-16T20:01:14Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [Streaming](), [Latency](), [client](), [servers](), [browser]() Tags: [browser](), [curl](), [firefox](), [http](), [http-workshop](), [latency](), [network](), [proxy](), [request](), [series](), [server](), [streaming](), [uploads](), [web]() ### AI overview A report from the third day of an HTTP workshop covering Media over QUIC transport, reverse HTTP, and resumable uploads. It discusses MOQ's proposed lower complexity and latency, server-initiated HTTP requests through CDN proxies, and an HTTP upload-resumption draft using Location, HEAD, and PATCH. ### Source excerpt See also: day one, day two. There is only one thing that is better than two days of HTTP workshop, and that is of course three days of HTTP workshop. The final day of this edition of the series started out with us again shuffling around where we parked ourselves around the big table. Except ... Continue reading Workshop Basel day three -> ## HTTP 206 Partial Content Explained DevFeed: [HTTP 206 Partial Content Explained]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-26T11:37:15Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [HTTP](), [client](), [browser](), [file](), [servers](), [Cache]() Tags: [browser](), [cache](), [cdn](), [client](), [file](), [http](), [http-206](), [http-codes](), [internet-architecture](), [large-files](), [range](), [request](), [server](), [video](), [web-servers](), [web-troubleshooting]() ### AI overview This tutorial explains HTTP 206 Partial Content, a successful response used when a client requests only part of a file or other resource. It describes byte-range requests, the Range and Content-Range headers, and uses such as video playback, resumable downloads, and cache or CDN handling. ### Source excerpt A browser does not always need the whole file at once. Sometimes it only needs a slice of the file. That slice might be the next part of a video or a chunk of a large object sitting behind a CDN. When that happens, the client can request a byte range instead of requesting the ... Read more The post HTTP 206 Partial Content Explained appeared first on Justin Wilson (j2sw). ## Nginx TLS tuning for HTTPS performance, TTFB, and latency DevFeed: [Nginx TLS tuning for HTTPS performance, TTFB, and latency]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-06-10T12:06:18Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [nginx](), [TLS (Transport Layer Security)](), [Latency](), [Handshake](), [HTTP](), [Back end]() Tags: [blog](), [encryption](), [http](), [http-3](), [latency](), [linux](), [nginx](), [performance](), [request](), [reuse](), [security](), [server](), [sysadmins](), [tls]() ### AI overview A practical guide to tuning Nginx TLS, HTTP/2, and HTTP/3 settings for HTTPS performance. It explains that tuning can reduce handshake overhead and improve connection reuse, while application execution often remains the main contributor to TTFB and latency. ### Source excerpt Nginx TLS tuning won't fix a slow application, but it does cut handshake overhead and improve connection reuse, which shaves milliseconds off every HTTPS request. Continue reading... ## 7 tips for using Figma Make credits more efficiently DevFeed: [7 tips for using Figma Make credits more efficiently]() Original publisher: [Read original article]() Author: Alexia Danton Published: 2026-05-22T12:00:00Z Content type: tutorial Language: en Sources: [Figma Blog]() Topics: [Figma](), [Code](), [ui]() Tags: [best-practices](), [code](), [component](), [context](), [cost](), [figma](), [prompting](), [request](), [screen](), [state](), [structure](), [tips](), [ui]() ### AI overview This tutorial presents seven practices for using Figma Make credits more efficiently. It recommends writing a complete initial prompt, keeping follow-up prompts focused and specific, building in stages, grouping related changes, and switching to direct editing for small visual adjustments. ### Source excerpt While everyone's talking about "tokenmaxxing," we've compiled seven best practices to help you build smarter--without prompting more--in Figma Make. ## How Spring Security Processes and Authorizes HTTP Requests DevFeed: [How Spring Security Processes and Authorizes HTTP Requests]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2026-04-30T15:54:51Z Content type: tutorial Language: en Sources: [Amigoscode Newsletter]() Topics: [Framework](), [Security](), [Authentication](), [HTTP]() Tags: [authentication](), [framework](), [http](), [request](), [security](), [spring]() ### AI overview This tutorial explains Spring Security as an ordered chain of servlet filters that processes each HTTP request before it reaches a controller. It covers the SecurityFilterChain, SecurityContextHolder, authentication filters, credential verification, and authorization checks. ### Source excerpt Walk a request through the chain end to end and the framework stops being magic. ## Anatomy of a trace DevFeed: [Anatomy of a trace]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-02T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [tracing](), [Traces](), [telemetry](), [API](), [Databases](), [Cache](), [Remote Procedure Call (RPC)](), [HTTP](), [SQL](), [Authentication]() Tags: [api](), [authentication](), [cache](), [database](), [distributed](), [http](), [request](), [rpc](), [sql](), [trace](), [tracing]() ### AI overview This article explains how distributed traces are built as requests move through services and operations. It describes root and child spans, trace IDs, automatic context propagation, and the operation-specific data captured by Encore's runtime, including API calls, RPCs, database queries, cache writes, and outbound HTTP calls. ### Source excerpt What actually happens when a request hits your application, and what a distributed trace captures at every step. ## Happy Teams Build Better Products DevFeed: [Happy Teams Build Better Products]() Original publisher: [Read original article]() Author: Raul Junco Published: 2025-12-12T12:38:14Z Content type: opinion Language: en Sources: [System Design Classroom]() Topics: [incident](), [debugging](), [Traces](), [telemetry](), [Tooling]() Tags: [context](), [debugging](), [incident](), [metrics](), [request](), [screenshots](), [teams](), [tools](), [traces]() ### AI overview An opinion article argues that engineering teams work better when they preserve incident context, use replays to reduce meetings, and consolidate debugging signals such as logs, traces, and metrics. ### Source excerpt 6 lessons every engineer eventually learns the hard way. ## Partial Function Application is coming in PHP 8.6 DevFeed: [Partial Function Application is coming in PHP 8.6]() Original publisher: [Read original article]() Author: Amit Merchant Published: 2025-12-05T00:00:00Z Content type: tutorial Language: en Sources: [Amit Merchant]() Topics: [PHP](), [PHP 8.6](), [Code](), [servers]() Tags: [argument](), [authorization](), [callback](), [closure](), [function](), [http](), [parameter](), [php](), [php-8-6](), [request](), [types]() ### AI overview This tutorial introduces Partial Function Application in PHP 8.6. It explains how placeholders create pre-configured Closures, covers multiple holes, named and variadic arguments, and shows a practical example for adding an Authorization header to HTTP requests. ### Source excerpt Ever reach for a simple callback and end up writing a tiny novella--an arrow function stuffed with types, reordered parameters, and boilerplate just to pass one value through? ## Трейсинг в hh.ru: как мы выросли от 1 тысячи до 1 миллиона событий в секунду без семплирования DevFeed: [Трейсинг в hh.ru: как мы выросли от 1 тысячи до 1 миллиона событий в секунду без семплирования]() Original publisher: [Read original article]() Author: Heruvimka (hh.ru, Конференции Олега Бунина (Онтико)) Published: 2025-09-16T09:00:45Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [observability](), [telemetry](), [SRE](), [Kafka](), [nginx](), [Apache Cassandra](), [OpenTelemetry](), [RabbitMQ]() Tags: [cassandra](), [devops](), [jaeger](), [kafka](), [nginx](), [observability](), [opentelemetry](), [operational-intelligence](), [rabbitmq](), [request](), [sre](), [tag-1e4ee1f65f5a](), [tag-68e701e78517](), [tag-73eb9b712998](), [tag-75f84211cab4](), [tag-8f8626975338](), [tag-9abb13e52060](), [tag-b92bf5906bbd](), [tag-d9df843a1803](), [tag-dfac9042ce7b](), [tracing]() ### AI overview This Russian developer article describes how hh.ru built and rebuilt its tracing and observability architecture as its data volume increased. The supplied text states that the system handles 24,000 RPS, one million spans per second, and 5,000 service instances, and introduces a log-based tracing design using Request-Id propagation. ### Source excerpt В каждой компании есть необходимость выстроить систему observability. В hh.ru мы перестраивали архитектуру под большее количество данных несколько раз -- сейчас имеем на входе 24к RPS, 1 миллион спанов в секунду, 5к инстансов сервисов. Если вы -- инженер, который находится в процессе построения или перестройки собственной системы трейсинга, этот доклад -- для вас. Привет, Хабр! Я -- Александр Казанцев, уже более десяти лет в разработке. Когда-то был инженером на пивзаводе и могу рассказать, из чего делают пенное; но сегодня -- о другом. Читать далее ## Implementing Model Monitoring on Databricks DevFeed: [Implementing Model Monitoring on Databricks]() Original publisher: [Read original article]() Author: Başak Tuğçe Eskili Published: 2025-08-06T16:55:23Z Content type: tutorial Language: en Sources: [MarvelousMLOps]() Topics: [databricks](), [MLOps](), [Monitoring](), [model-serving](), [dashboards](), [Inference](), [Logging](), [Data Quality]() Tags: [databricks](), [metrics](), [mlops](), [model-monitoring](), [model-serving](), [monitoring](), [request](), [table]() ### AI overview Lecture 10 in an MLOps with Databricks course demonstrates model monitoring using inference tables and Lakehouse Monitoring. It covers collecting inference logs, creating a structured monitoring table, scheduling refreshes, and building a dashboard to visualize metrics and detect drift. ### Source excerpt Lecture 10 of MLOps with Databricks course ## Shadow Repeater:AI-enhanced manual testing DevFeed: [Shadow Repeater:AI-enhanced manual testing]() Original publisher: [Read original article]() Author: Gareth Heyes Published: 2025-02-20T13:20:19Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [Artificial Intelligence](), [Testing](), [Vulnerabilities](), [Extension](), [Code]() Tags: [ai](), [attacks](), [automatic](), [code](), [extension](), [github](), [request](), [testing](), [vulnerabilities](), [xss]() ### AI overview Shadow Repeater is a Burp Repeater extension that enhances manual security testing with AI-powered automatic variation testing. It analyzes changed parameters and payloads, generates variants through an AI model, tests them against the target, and uses response diffing to identify potentially interesting behavior and vulnerabilities. ### Source excerpt Have you ever wondered how many vulnerabilities you've missed by a hair's breadth, due to a single flawed choice? We've just released Shadow Repeater, which enhances your manual testing with AI-powere ## How Request processing has changed over the years DevFeed: [How Request processing has changed over the years]() Original publisher: [Read original article]() Published: 2025-02-03T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [processing](), [Computer science](), [Concurrency](), [scheduling](), [Kernel](), [Processes](), [Ruby](), [Python]() Tags: [concurrency](), [cpu](), [kernel](), [process](), [processing](), [python](), [request](), [ruby](), [scheduling]() ### AI overview This article explains how web request processing works, distinguishing blocking and non-blocking tasks and introducing concepts such as CPU control, kernel behavior, and cooperative versus preemptive scheduling. It begins comparing request-processing architectures in the context of Ruby, Python, NodeJS, and Rails services. ### Source excerpt . [How Request Processing Has Changed Over the Years](how-request-processing-has-changed-over-the-years-cover... ## Heroku Investigates Puma Bug Causing High Response Times with Router 2.0 DevFeed: [Heroku Investigates Puma Bug Causing High Response Times with Router 2.0]() Original publisher: [Read original article]() Author: Elizabeth Cox Published: 2024-11-21T18:13:05Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Ruby](), [Rails](), [HTTP](), [servers]() Tags: [applications](), [article](), [bug](), [cloud-infrastructure](), [dashboards](), [dynos](), [engineering](), [heroku](), [http](), [improvements](), [legacy](), [load](), [performance](), [request](), [router](), [router-2-0](), [ruby](), [server](), [technical](), [update](), [upgrade]() ### AI overview Heroku investigates a Puma bug that caused elevated response times for a small subset of applications after enabling Router 2.0. The article explains the investigation, reproduction conditions, mitigation guidance, and the subsequent Puma 7.0 fix. ### Source excerpt Update: Puma 7.0 was released with a fix for the bug described in this article. We recommend Ruby applications upgrade to Puma 7.0.4 or higher. This week, Heroku made Router 2.0 generally available, bringing features like HTTP/2, performance improvements and reliability enhancements out of the beta program! Throughout the Router 2.0 beta, our engineering team [...] The post Pumas, Routers & Keepalives--Oh my! appeared first on Heroku. [Next page]()