# HTTP Published articles for HTTP. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Most Simple Ajax Chat Ever DevFeed: [Most Simple Ajax Chat Ever]() Original publisher: [Read original article]() Author: Chris Hager Published: 2026-09-17T02:48:44.791916Z Content type: article Language: en Sources: [Chris Hager]() Topics: [Ajax](), [PHP](), [HTML](), [Code]() Tags: [code](), [files](), [github](), [html](), [http](), [php]() ### AI overview A project page describing a simple Ajax chat application created in January 2006. It explains the two-file implementation, pure JavaScript approach without libraries, text-based content storage, spam filtering, and two-step PHP setup. ### Source excerpt Most Simple Ajax Chat Ever A fun little project from January 2006. Back then ajax just started becoming popular, but with very few tools around. jQuery came out later that year, Github just two years later, in 2008. Original code on Github Original site on web.archive.org Featured on Wired in February 2006 Features Super simple Efficient spam filter (thanks to some live 'hackers' at launch) Only 2 files needed (index.html, w. ## Agents at Large | Tracing Illicit OpenAI Agent Activity on Hugging Face DevFeed: [Agents at Large | Tracing Illicit OpenAI Agent Activity on Hugging Face]() Original publisher: [Read original article]() Author: Tom Hegel Published: 2026-09-16T10:00:34Z Content type: article Language: en Sources: [SentinelLabs - We are hunters, reversers, exploit developers, and tinkerers shedding light on the world of malware, exploits, APTs, and cybercrime across all platforms.]() Topics: [Threat Research](), [Incident response](), [hugging face](), [OpenAI](), [ChatGPT](), [spaces](), [Flask](), [OAuth](), [HTTP]() Tags: [agentic-ai](), [agents](), [chatgpt](), [flask](), [http](), [hugging-face](), [incident-response](), [oauth](), [openai](), [research](), [spaces](), [token]() ### AI overview SentinelLABS traces activity associated with two Hugging Face accounts, 0Time and Nyx9, that appears to extend OpenAI's published chronology. The report describes relay-code commits, a workbook containing unexecuted-looking external probes, and a Flask-wrapped tool that could potentially provision ChatGPT identities or OAuth credentials if deployed and invoked. ### Source excerpt Two Hugging Face accounts reveal that OpenAI's agents staged relay code, internal probes and ChatGPT account registration beyond the published timeline. ## JavaScript bundling and HTTP performance trade-offs DevFeed: [JavaScript bundling and HTTP performance trade-offs]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-11-23T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [JavaScript](), [HTTP](), [Caching](), [browserify](), [Webpack]() Tags: [browserify](), [cache](), [engineering](), [http](), [infrastructure](), [js](), [news](), [webpack]() ### AI overview The article examines trade-offs between bundling JavaScript files, serving them separately, and using semantically related bundles. It explains how these approaches balance HTTP request overhead, browser fetch limits, cacheability, and unused downloaded code. ### Source excerpt By Craig Silverstein Bundling JavaScript files The traditional advice for web developers is to bundle the JavaScript files ... Read more ## Kotlin on the server at Khan Academy DevFeed: [Kotlin on the server at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-06-28T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Kotlin](), [backend-development](), [Python](), [Google]() Tags: [api](), [bigquery](), [blog-post](), [developer-experience](), [engineering](), [google](), [http](), [infrastructure](), [java](), [kotlin](), [news](), [python](), [server-side-development]() ### AI overview Khan Academy describes testing Kotlin for user-facing server requests during a 2018 hackathon and deciding to adopt Kotlin as a second server-side language after reporting positive efficiency results and a positive developer experience. ### Source excerpt By Colin Fuller At Khan Academy, we run our web application using Python 2.7 on Google's App Engine ... Read more ## CodeSOD: Extremely One Line DevFeed: [CodeSOD: Extremely One Line]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-16T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [ASP.NET](), [Code](), [Visual Studio](), [Command-line interface](), [browser](), [HTTP]() Tags: [asp-net](), [browser](), [cli](), [code](), [codesod](), [http](), [studio]() ### AI overview This CodeSOD commentary examines an ancient ASP .Net application containing a function written on one line, Safari user-agent detection, and a mysterious "uplevel" value. It criticizes the confusing style and notes that the same pattern appears on multiple pages. ### Source excerpt Autoformatting your code is a standard thing to do these days. And in those days past, if we're being honest. There's no excuse to not use some kind of autoformatter. Whether you configure your editor to do it or are a weirdo like me who runs a formatter from the CLI as a build step, you've got an easy way to format your code so it looks neat and readable. And some IDEs, like Visual Studio, are pretty insistent about doing this for you. Which makes today's code sample a bit more perplexing. This comes from an ancient ASP .Net application that Austin has the misfortune to work with: protected void Page_PreInit(object sender, EventArgs e){if (Request.ServerVariables["http_user_agent"].IndexOf("Safari", StringComparison.CurrentCultureIgnoreCase) != -1)Page.ClientTarget = "uplevel";} protected void Page_Load(object sender, EventArgs e) { Logic(); } Which function is Logic() called from? The fact that I'm asking probably is enough to get you to scroll over. The entire Page_PreInit function is on a single line, followed by the declaration of the Page_Load function. A confusing and annoying choice. The real bonus is that if the browser has "Safari" in its user agent, we set a field to a mysterious "uplevel" value. A mix of user agent sniffing, strings as enums/flags, and wonderfully unclear names. And yes, this particular pattern appears in more than one page in Austin's application. Someone thought this was not just a good idea, but good enough to do over and over again. [Advertisement] Picking up NuGet is easy. Getting good at it takes time. Download our guide to learn the best practice of NuGet for the Enterprise. ## 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. ## How WebRTC Scales: Signaling, NAT Traversal, and the Mesh/SFU/MCU Tradeoff DevFeed: [How WebRTC Scales: Signaling, NAT Traversal, and the Mesh/SFU/MCU Tradeoff]() Original publisher: [Read original article]() Author: Karan Pratap Singh Published: 2026-09-15T15:57:39Z Content type: article Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [WebRTC](), [real-time](), [browsers](), [API](), [JavaScript](), [WebSocket](), [Firewall](), [Network](), [servers]() Tags: [api](), [browsers](), [decoding](), [distributed-system](), [firewall](), [http](), [javascript](), [network](), [networking](), [real-time](), [server](), [webrtc]() ### AI overview This article explains how WebRTC enables browsers to exchange audio, video, and data directly. It covers the three WebRTC APIs, signaling through WebSockets or HTTP, NAT traversal using ICE, STUN, and TURN, and the mesh, SFU, and MCU approaches to scaling media delivery. ### Source excerpt Web Real-Time Communication (or WebRTC) is the open standard browsers use to send audio, video, and data straight to each other. There's no plugin or native app, nothing beyond an API that every brows ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory]() Original publisher: [Read original article]() Author: Amanda Lange, Dhruv Patel Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Node.js](), [Large Language Model](), [Express](), [OpenAI](), [API](), [WebSocket](), [Machine learning]() Tags: [api](), [axios](), [console](), [developer-insights](), [environment-variables](), [express](), [how-to](), [http](), [ide](), [install](), [js](), [json](), [llm](), [ngrok](), [node-js](), [npm](), [openai](), [rest-api](), [sdk](), [visual-studio-code](), [web]() ### AI overview This tutorial shows how to build a Node.js Express service that uses Twilio Conversation Memory, OpenAI, and voice streams to preserve caller context, preferences, and action history across separate inbound calls. It covers project setup, package installation, local webhook exposure with ngrok, and access to Twilio's Conversation Memory REST API. ### Source excerpt Learn how to orchestrate multi-call voice conversations using Node.js, OpenAI, and Twilio Conversation Memory to persist caller context across separate calls. ## A Week of Symfony #1028 (September 7-13, 2026) DevFeed: [A Week of Symfony #1028 (September 7-13, 2026)]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-13T07:05:00Z Content type: news Language: en Sources: [Symfony Blog]() Topics: [Code](), [OAuth 2.0](), [OpenID connect (OIDC)](), [Security]() Tags: [cache](), [code](), [development](), [docs](), [http](), [pull-requests](), [security](), [symfony]() ### AI overview Symfony's weekly roundup covers standalone framework bundles, Docker-style console subcommands, expanded OAuth2 and OpenID Connect support, and SymfonyCon Warsaw 2026 announcements. It also reports merged pull requests, closed issues, and selected development fixes. ### Source excerpt This week, Symfony introduced standalone bundles for the framework features (MessengerBundle, HttpClientBundle, PropertyInfoBundle, etc.), added Docker-style console subcommands, and expanded OAuth2 and OpenID Connect support. In addition, we announced the... ## Scaling AI Agent Infrastructure with the MCP Stateless updates DevFeed: [Scaling AI Agent Infrastructure with the MCP Stateless updates]() Original publisher: [Read original article]() Author: Kurtis Van Gent; Alan Blount Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [networking](), [SDKs]() Tags: [agentic](), [ai-agent](), [c-sharp](), [go](), [http](), [infrastructure](), [mcp](), [python](), [routing](), [sdks](), [serverless](), [typescript](), [updates]() ### AI overview The MCP release candidate replaces transport-level session management with a stateless core for HTTP load balancing, cloud-native scaling, and serverless deployments. It also introduces routing headers, caching controls, MRTR, and beta SDKs for Python, TypeScript, Go, and C#. ### Source excerpt The 2026-07-28 Model Context Protocol (MCP) specification replaces legacy stateful constraints with a fully stateless core, enabling cloud-native horizontal scaling, serverless deployments, and standard round-robin load balancing. This architectural shift introduces standardized HTTP headers for efficient routing without deep packet inspection, caching controls, and Multi Round-Trip Requests (MRTR) to handle interactive and long-running tasks without blocking connections. Developers can immediately begin migrating their agentic applications to this highly scalable infrastructure using the newly available beta SDKs for Python, TypeScript, Go, and C#. ## HTTP/3 Support in HTTP Client API in Java 26 DevFeed: [HTTP/3 Support in HTTP Client API in Java 26]() Original publisher: [Read original article]() Author: Rajat Garg Published: 2026-09-10T18:50:56Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Java HttpClient](), [client](), [Networks](), [Latency]() Tags: [api](), [http](), [java](), [java-httpclient](), [latency](), [networking](), [networking-java-httpclient](), [networks](), [popular](), [tls](), [tutorial]() ### AI overview A tutorial on using Java 26's HttpClient API with HTTP/3, including protocol preference and server-support discovery. ### Source excerpt Learn how HttpClient API supports HTTP/3 now, and how to set your apps to use HTTP/3. The post HTTP/3 Support in HTTP Client API in Java 26 first appeared on Baeldung. ## APIs & Service Communication: The Essential Guide DevFeed: [APIs & Service Communication: The Essential Guide]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-08T13:03:41Z Content type: tutorial Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [API](), [Microservice](), [GraphQL](), [gRPC](), [Kafka](), [WebSocket]() Tags: [api](), [apis](), [graphql](), [http](), [kafka](), [rest]() ### AI overview A tutorial comparing communication patterns for distributed systems. It explains how request-response APIs, event streams, and bidirectional connections affect responsiveness, service coupling, failure propagation, operational complexity, reliability, and scalability, then introduces REST and GraphQL with their main strengths, tradeoffs, and use cases. ### Source excerpt REST, gRPC, Kafka, WebSockets, Pub/Sub, and more. How do they all fit together? ## Debug Past an HTTP 403 Without Breaking Spring Security DevFeed: [Debug Past an HTTP 403 Without Breaking Spring Security]() Original publisher: [Read original article]() Author: Andrey Belyaev Published: 2026-09-08T12:34:18Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [debug](), [Authorization](), [IntelliJ IDEA](), [ide]() Tags: [debug](), [features](), [http](), [intellij-idea](), [security](), [spring](), [spring-debugger](), [tutorials]() ### AI overview The article explains how IntelliJ IDEA security inlays help debug Spring endpoints blocked by HTTP 403, 401, or login redirects. It covers inspecting runtime role requirements and temporarily unlocking an endpoint for a debug session, with a warning that unlocking affects all clients reaching that URI and method. ### Source excerpt You set a breakpoint inside a Spring MVC controller, or a service, send the request to an HTTP endpoint, and nothing happens. The response is back - and it is a 403 (or 401, or a redirect to a login page). At that point, the bug you were trying to catch is no longer the [...] ## What Is the x402 Protocol? HTTP 402 Payments for AI Agents DevFeed: [What Is the x402 Protocol? HTTP 402 Payments for AI Agents]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [AI Agent](), [API](), [client](), [Model Context Protocol]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [ai-agents](), [api](), [autonomous](), [coinbase](), [guide](), [http](), [mcp](), [model-context-protocol](), [payments](), [tools]() ### AI overview A technical guide to x402, an open payment standard that uses HTTP 402 to let clients pay for individual API requests without accounts, API keys, sessions, or subscriptions. It explains the payment handshake, the roles of clients, resource servers, and facilitators, plus x402's use over HTTP, MCP, and A2A transports. ### Source excerpt A technical guide to the x402 protocol: how the HTTP 402 payment handshake works, the PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers, facilitators, payment schemes, and where x402 fits next to card rails. ## Testing the Swagger Petstore: Manually Testing An API Using Swagger UI DevFeed: [Testing the Swagger Petstore: Manually Testing An API Using Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-07T16:43:41Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Swagger](), [Testing](), [API](), [OpenAPI Specification]() Tags: [api](), [auth](), [authentication](), [authorization](), [http](), [openapi](), [payload](), [schema](), [swagger](), [testing](), [ui]() ### AI overview A practical guide to manually testing the Swagger Petstore API through Swagger UI. It covers happy-path, negative, boundary and edge-case, authentication and authorization, and contract and schema validation tests using the browser-based "Try it out" feature. ### Source excerpt With the last post, Testing the Swagger Petstore: Reviewing API Documentation Formatted in OpenAPI 3.0 with Swagger UI we started exploring an API with Swagger UI, such as the Swagger Petstore at https://petstore3.swagger.io/ Here, we will start exploring how to test an API using the Swagger UI. The tests we can run are: Happy Path Testing, checking the Positive Scenarios Negative Testing, reviewing the Invalid Inputs & Error Handling Boundary & Edge Case Testing, checking how the API handles the extreme limits of allowed input ranges Authentication & Authorization Testing Contract and schema validation We can see in the Swagger PetStore there are three tag groups: Pet, Store, and User. Because this is a Swagger UI doc, we can perform manual testing using only the "Try it out" feature in Swagger UI. No external tools needed! Live HTTP requests can be executed directly from your browser. Types of Testing for the API Here are a few types of testing and examples you can do in Swagger UI Happy path Functional Testing Pet POST /pet: add a new pet with a complete, valid payload. Verify 200 and that the response echoes the submitted fields. PUT /pet: update the pet you just created. Verify the change persists on a follow-up GET. GET /pet/{petId}: retrieve the pet by the ID returned from the POST. GET /pet/findByStatus: query with each valid status value (available, pending, sold) individually. GET /pet/findByTags: query with a tag that exists on a pet you created. POST /pet/{petId} (form data): update name/status via form fields instead of JSON body. POST /pet/{petId}/uploadImage: upload a valid image file, verify response message and metadata. DELETE /pet/{petId}: delete a pet you created, then confirm GET on that ID now fails. Store POST /store/order: place an order with valid petId, quantity, shipDate, status. GET /store/order/{orderId}: retrieve the order just placed. GET /store/inventory: verify it returns a status-to-count map without needing auth. DELETE /store/orde ## One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice DevFeed: [One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-07T09:27:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [OpenAPI Specification](), [Model Context Protocol (MCP)](), [MCP Server](), [API](), [ASCII](), [HTTP](), [cURL]() Tags: [ai-gateway](), [ai-governance](), [ai-readiness](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [article](), [ascii](), [curl](), [developer](), [http](), [llm-governance](), [llm-observability](), [mcp-server](), [model-context-protocol](), [openapi]() ### AI overview This tutorial shows how to define an HTTP API once in an OpenAPI document and expose it through three surfaces: model-initiated tool calls, a REST endpoint accessed with curl, and an MCP server. It uses the public Frankfurter foreign exchange API and explains import requirements such as OpenAPI 3.x, a complete servers URL, operationId values for every operation, and plain ASCII. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a genuinely satisfying assignment. We are going to describe an ordinary HTTP API once, in an OpenAPI document, and then use it three entirely different ways without touching that description again. A model will call it on its own initiative inside a chat. [...] The post One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice appeared first on Tyk API Management. ## A countdown that stays accurate in a background tab DevFeed: [A countdown that stays accurate in a background tab]() Original publisher: [Read original article]() Author: Marko Published: 2026-09-05T06:30:19Z Content type: tutorial Language: en Sources: [Marko Denic Tech]() Topics: [web applications](), [client](), [Server]() Tags: [blog-for-developers](), [browsers](), [bug](), [build-faster](), [code-productivity](), [code-smarter](), [content-monetization](), [css-animation](), [css-performance](), [developer-growth](), [developer-resources](), [email-newsletter-for-coders](), [front-end-development](), [github-profile-automation](), [html](), [html-tips](), [http](), [javascript](), [javascript-tricks](), [learn-to-code](), [responsive-design-tips](), [server](), [ui](), [web-dev-newsletter](), [web-development](), [web-development-tips](), [weekly-dev-tips](), [workflow-optimization]() ### AI overview A tutorial on building accurate web countdowns despite background-tab timer throttling. It recommends calculating remaining time from an absolute deadline, forcing a render when a tab returns, and treating the server clock as the authority for consequential expirations. ### Source excerpt Your checkout timer says 4:55 when the cart already expired. Why background tabs break setInterval countdowns, and the three-line fix. ## ClickHouse as a streaming HTTP API DevFeed: [ClickHouse as a streaming HTTP API]() Original publisher: [Read original article]() Author: Mark Needham Published: 2026-09-05T00:00:00Z Content type: tutorial Language: en Sources: [ClickHouse Blog]() Topics: [web applications]() Tags: [api](), [architecture](), [clickhouse](), [data](), [features](), [how-to](), [http](), [streaming](), [validation]() ### AI overview A tutorial on using ClickHouse 26.8 to expose controlled queries as a streaming HTTP API with named HTTP handlers, access control, and result limits. ### Source excerpt Learn how to build a streaming HTTP API directly in ClickHouse 26.8 with named handlers, typed parameters, pagination, framing formats, and access control. ## 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? ## Turn your app into an MCP server with the Appwrite OAuth2 server DevFeed: [Turn your app into an MCP server with the Appwrite OAuth2 server]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Model Context Protocol](), [OAuth 2.0](), [Authorization](), [Claude Code](), [Serverless](), [web applications](), [Databases]() Tags: [ai](), [ai-tools](), [app](), [auth](), [authorization](), [browser](), [claude](), [claude-code](), [code](), [databases](), [http](), [mcp](), [mcp-server](), [oauth2](), [remote-mcp-server](), [serverless](), [tutorial](), [tutorials](), [web](), [web-app]() ### AI overview This tutorial explains how to turn an Appwrite-based application into a remote MCP server. It uses an Appwrite Function, the OAuth2 server included in an Appwrite project, and a consent screen so AI tools such as Claude Code can access and act on behalf of signed-in users. ### Source excerpt Build a remote MCP server for your product, host it on Appwrite Functions, and let AI tools like Claude Code sign in through the OAuth2 server built into your Appwrite project. ## Fixed window, sliding window, or token bucket? Choosing a rate limit strategy in Appwrite Firewall DevFeed: [Fixed window, sliding window, or token bucket? Choosing a rate limit strategy in Appwrite Firewall]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Firewall](), [Algorithms](), [HTTP](), [client]() Tags: [firewall](), [http](), [rate-limiting](), [security](), [strategy]() ### AI overview This article explains the fixed window, sliding window, and token bucket rate-limiting strategies supported by Appwrite Firewall. It compares how they handle bursts and time-window boundaries, describes IP- and User ID-based limits, and explains how to choose a strategy. ### Source excerpt Appwrite Firewall rate limit rules support three strategies. Learn how fixed window, sliding window, and token bucket work, where each one breaks down, and how to pick the right one for your traffic. ## How Turbopack chunks your JavaScript DevFeed: [How Turbopack chunks your JavaScript]() Original publisher: [Read original article]() Author: Sam Poder Published: 2026-09-03T16:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [modern web development](), [Web Development](), [web applications]() Tags: [cache](), [code](), [compression](), [http](), [javascript](), [next-js]() ### AI overview The article explains how Turbopack groups JavaScript into chunks for Next.js applications. It examines the tradeoff between minimizing downloaded code and minimizing network requests, including the effects on caching and compression. ### Source excerpt Turbopack's chunking speeds up page loads and enables sharing code across pages. We shipped new experimental features to improve chunking in Next.js 16.3. ## MCP Went Stateless: What Now? DevFeed: [MCP Went Stateless: What Now?]() Original publisher: [Read original article]() Author: Janet Wagner Published: 2026-09-03T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Model Context Protocol (MCP)](), [Scalability](), [MCP Server](), [Architecture & Design](), [Security](), [Tool]() Tags: [ai](), [ai-agents](), [api-gateway](), [api-security](), [api-standards](), [artificial-intelligence](), [blog](), [cloud-native](), [developers](), [http](), [llm](), [mcp](), [mcp-server](), [model-context-protocol](), [scalability](), [security](), [strategy]() ### AI overview The article examines the shift to stateless MCP and its implications for scalability, state management, security, gateways, and MCP server architecture. ### Source excerpt The latest release of the Model Context Protocol (MCP) specification has created a lot of buzz in tech circles. Why? Primarily because this AI communication protocol has now gone stateless! This shift from stateful to stateless impacts how developers of MCP servers and AI tools use the protocol moving forward. In addition, the change impacts ... ## curl 8.22.0 DevFeed: [curl 8.22.0]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-09-02T05:52:46Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Security](), [HTTP](), [openssl](), [API](), [TLS (Transport Layer Security)](), [Command-line interface]() Tags: [bugfixes](), [command-line](), [curl](), [curl-and-libcurl](), [cve](), [cves](), [http](), [openssl](), [release](), [security](), [tls]() ### AI overview The curl 8.22.0 release includes six changes, 302 bug fixes, and nine curl/libcurl security fixes plus one wcurl fix. It adds Apple GSS Framework support, API guards, experimental HTTP Message Signatures support, and Apple fast UDP, while blocking NTLM fallback in SPNEGO and dropping TLS-SRP support. ### Source excerpt Welcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new ... Continue reading curl 8.22.0 -> [Next page]()