# WebSocket

WebSocket is a protocol for two-way client-server communication over TCP, with a browser API for web applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CVE-2026-77359 - Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

DevFeed: [CVE-2026-77359 - Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes](<https://devfeed.tech/articles/cve-2026-77359-jupyter-mcp-server-browser-dns-rebinding-can-hijack-the-jupyter-backend-through-management-routes-143946.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-77359>)

Author: CVEFEED.io; github.com

Published: 2026-11-19T17:18:59Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-connect](<https://devfeed.tech/tags/api-connect.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bind](<https://devfeed.tech/tags/bind.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [browser](<https://devfeed.tech/tags/browser.md>), [client](<https://devfeed.tech/tags/client.md>), [connect](<https://devfeed.tech/tags/connect.md>), [container](<https://devfeed.tech/tags/container.md>), [controls](<https://devfeed.tech/tags/controls.md>), [cve-2026-77359](<https://devfeed.tech/tags/cve-2026-77359.md>), [datalayer](<https://devfeed.tech/tags/datalayer.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-rebinding](<https://devfeed.tech/tags/dns-rebinding.md>), [hijack](<https://devfeed.tech/tags/hijack.md>), [jupyter](<https://devfeed.tech/tags/jupyter.md>), [jupyter-mcp-server](<https://devfeed.tech/tags/jupyter-mcp-server.md>), [management](<https://devfeed.tech/tags/management.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

Before version 1.0.3, standalone streamable-HTTP mode in Jupyter MCP Server checks Host and Origin on /mcp but lacks the same browser-origin controls on the state-changing /api/connect and /api/stop routes. A malicious site can use DNS rebinding to reach an exposed listener and submit a browser-shaped /api/connect request that changes runtime_url and document_url, directing Jupyter API and WebSocket traffic to attacker-controlled infrastructure. It can also use /api/stop to stop the current notebook kernel. A broad default bind can increase exposure; the described flaw is the missing origin boundary on the management routes. The issue is fixed in 1.0.3.

### Source excerpt

CVE ID :CVE-2026-77359 Published : Nov. 19, 2026, 5:18 p.m. | 26 minutes ago Description :Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website can use DNS rebinding so that its hostname resolves to a loopback, LAN, VPN, or published-container MCP listener, then send a browser-shaped request that /api/connect accepts to replace runtime_url and document_url values and start a kernel client against attacker-controlled infrastructure. The attacker can thereby cause Jupyter API and WebSocket traffic to reach that infrastructure and can use /api/stop to stop the current notebook kernel. The default broad bind can increase exposure, but the vulnerability is the missing management-route origin boundary, not a lack of Host validation on /mcp. This issue is fixed in version 1.0.3. Severity: 9.3 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-102612 - BACnet Stack: BACnet/SC hub never requires a client cert, so any host joins the mesh unauthenticated

DevFeed: [CVE-2026-102612 - BACnet Stack: BACnet/SC hub never requires a client cert, so any host joins the mesh unauthenticated](<https://devfeed.tech/articles/cve-2026-102612-bacnet-stack-bacnet-sc-hub-never-requires-a-client-cert-so-any-host-joins-the-mesh-unauthenticated-132626.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-102612>)

Author: CVEFEED.io; github.com

Published: 2026-11-13T19:17:37Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [bacnet-stack](<https://devfeed.tech/tags/bacnet-stack.md>), [bacnetstack](<https://devfeed.tech/tags/bacnetstack.md>), [c](<https://devfeed.tech/tags/c.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-102612](<https://devfeed.tech/tags/cve-2026-102612.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cwe](<https://devfeed.tech/tags/cwe.md>), [embedded-systems](<https://devfeed.tech/tags/embedded-systems.md>), [hub](<https://devfeed.tech/tags/hub.md>), [library](<https://devfeed.tech/tags/library.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [patched](<https://devfeed.tech/tags/patched.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [server](<https://devfeed.tech/tags/server.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

Before BACnet Stack versions 1.4.6, 1.5.2, and 1.6.1, bws_srv_start() created the BACnet/SC hub's libwebsockets server context with a CA certificate but did not require a valid client certificate. As a result, any network-reachable host could connect to the mesh without credentials. The issue is patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0. The supplied text rates it HIGH, with a score of 8.1.

### Source excerpt

CVE ID :CVE-2026-102612 Published : Nov. 13, 2026, 7:17 p.m. | 13 minutes ago Description :BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.6, 1.5.2, and 1.6.1, bws_srv_start() in ports/linux/websocket-srv.c builds the libwebsockets server context with a CA certificate loaded but never sets LWS_SERVER_OPTION_REQUIRE_VALID_OPENSSL_CLIENT_CERT, so the hub accepts TLS connections from clients presenting no certificate at all. Any network-reachable host can join the BACnet/SC mesh without credentials. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Kubernetes Python client gets a modern overhaul for the AI/ML era

DevFeed: [Kubernetes Python client gets a modern overhaul for the AI/ML era](<https://devfeed.tech/articles/kubernetes-python-client-gets-a-modern-overhaul-for-the-ai-ml-era-132589.md>)

Original publisher: [Read original article](<http://opensource.googleblog.com/2026/11/kubernetes-python-client-modern-overhaul-ai-ml.html>)

Author: Google Open Source (noreply@blogger.com)

Published: 2026-11-12T19:30:00Z

Content type: article

Language: en

Sources: [Google Open Source Blog](<https://devfeed.tech/sources/google-open-source-blog.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [distributed-training](<https://devfeed.tech/topics/distributed-training.md>), [Gke](<https://devfeed.tech/topics/gke.md>), [KServe](<https://devfeed.tech/topics/kserve.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code-generator](<https://devfeed.tech/tags/code-generator.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [modernize](<https://devfeed.tech/tags/modernize.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

The official Kubernetes Python client is being modernized with Google Cloud engineers and Kubernetes SIG API Machinery contributors to address limitations exposed by large AI/ML clusters. The excerpt identifies a deprecated OpenAPI Generator v4.3.0 pipeline, lack of native asyncio and SharedInformer support, legacy SPDY streaming, and slow JSON model deserialization; pod and node listings could take 30+ seconds. The effort targets high-impact Python workload needs rather than full client-go parity. Its roadmap includes moving to OpenAPI Generator v7.20+, adding official asyncio, list-watch Shared Informers with caching and event handlers, and WebSocket v5 support for exec, attach, and port-forward. It also aims to reduce deserialization overhead. These are described as ongoing modernization work and goals; the excerpt does not report completed performance results.

### Source excerpt

by Yu Liao, Haowei Cai, and Federico Bongiovanni, Google Cloud Kubernetes Engineering & SIG API Machinery When you train a large language model with Kubeflow, orchestrate distributed compute with Ray on Google Kubernetes Engine (GKE), serve inference traffic with KServe, or schedule thousands of ML pipeline pods with Apache Airflow, two technologies almost always meet under the hood: Python and Kubernetes. Python is the undisputed lingua franca of artificial intelligence and machine learning. Kubernetes is the de facto operating system for AI infrastructure--scheduling GPUs and TPUs, orchestrating distributed training jobs, and scaling model serving endpoints. Connecting these two worlds is the official Kubernetes Python client (kubernetes-client/python). Second only to Kubernetes's in-tree Go client (client-go) in popularity, the Kubernetes Python client is downloaded more than 73 million times per month on PyPI (~1.7 million times a day) and has earned over 7,500 GitHub stars. Yet for the past several years, this critical bridge between Python and Kubernetes has operated in low-maintenance mode. As AI/ML workloads have exploded in scale and complexity, the gap between what modern AI infrastructure demands and what the legacy Python client was built to deliver has become impossible to ignore. Today, we're sharing how Google Cloud engineers are partnering with open source contributors in Kubernetes SIG API Machinery to modernize the official Kubernetes Python client for the AI/ML era. The historical problem: Legacy machinery meets hyperscale AI As AI/ML clusters grew from dozens of nodes to 50,000-node hyperscale environments, the limitations of the Python client's aging architecture began surfacing as real-world production bottlenecks: Frozen on a decommissioned code generator: Up through Kubernetes 1.35, the Python client generated its ~400,000 lines of API and model code using OpenAPI Generator v4.3.0 (python-legacy)--a generator version that was deprecated in 2020

## The XG Files: Falcon C2 Flying Under The (Browser) Radar

DevFeed: [The XG Files: Falcon C2 Flying Under The (Browser) Radar](<https://devfeed.tech/articles/the-xg-files-falcon-c2-flying-under-the-browser-radar-129332.md>)

Original publisher: [Read original article](<https://unit42.paloaltonetworks.com/falcon-c2-browser-compromise/>)

Author: Unit 42

Published: 2026-11-11T15:00:23Z

Content type: news

Language: en

Sources: [Unit 42](<https://devfeed.tech/sources/unit-42.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [Chrome extension](<https://devfeed.tech/topics/chrome-extension.md>), [Docro Hijacker](<https://devfeed.tech/topics/docro-hijacker.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Firefox extension](<https://devfeed.tech/topics/firefox-extension.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [adobe-flash-player](<https://devfeed.tech/tags/adobe-flash-player.md>), [based](<https://devfeed.tech/tags/based.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-extension](<https://devfeed.tech/tags/browser-extension.md>), [c2](<https://devfeed.tech/tags/c2.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [dll-sideloading](<https://devfeed.tech/tags/dll-sideloading.md>), [exfiltration](<https://devfeed.tech/tags/exfiltration.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [falcon](<https://devfeed.tech/tags/falcon.md>), [files](<https://devfeed.tech/tags/files.md>), [framework](<https://devfeed.tech/tags/framework.md>), [implant](<https://devfeed.tech/tags/implant.md>), [json](<https://devfeed.tech/tags/json.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [proxy-server](<https://devfeed.tech/tags/proxy-server.md>), [radar](<https://devfeed.tech/tags/radar.md>), [threat-research](<https://devfeed.tech/tags/threat-research.md>), [web-server](<https://devfeed.tech/tags/web-server.md>), [xor](<https://devfeed.tech/tags/xor.md>)

### AI overview

Unit 42 reports that Falcon (XG/Xiàng Gē) is a browser based C2 framework used in campaigns against government entities in at least five countries. Malicious scripts injected into web portals run in victims' browser tabs, while Chrome and Firefox extensions can expand access to credentials, cookies, page traffic, downloads, clipboard data, and selected communications. Falcon maintains browser sessions over encrypted WebSockets; its Comet fallback does not encrypt exchanged payloads. The researchers assess with high confidence that Falcon and PeckBirdy are variants of the same core framework, citing overlapping URLs, delivery methods, protocols, and session ID naming. In one campaign, Falcon delivered Antino, a Rust implant that persists through a Windows Registry Run key and uses Microsoft OneDrive for command and control. Reported activity included webmail credential interception, username harvesting, extension based access, and collection from internal justice department systems. The article recommends monitoring for suspicious developer mode extensions, Hm_lvt_ storage keys, injected scripts on internal portals, and anomalous OneDrive activity. These findings and recommendations

### Source excerpt

We uncover Falcon C2, a browser-based threat framework targeting governments via malicious scripts, extensions, and the Antino implant. The post The XG Files: Falcon C2 Flying Under The (Browser) Radar appeared first on Unit 42.

## Workflow SDK now writes over WebSockets on Vercel

DevFeed: [Workflow SDK now writes over WebSockets on Vercel](<https://devfeed.tech/articles/workflow-sdk-now-writes-over-websockets-on-vercel-124310.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/workflow-writes-now-use-websockets-on-vercel>)

Author: Shalabh Chaturvedi

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [costs](<https://devfeed.tech/tags/costs.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [event](<https://devfeed.tech/tags/event.md>), [existing](<https://devfeed.tech/tags/existing.md>), [faster](<https://devfeed.tech/tags/faster.md>), [fewer](<https://devfeed.tech/tags/fewer.md>), [http](<https://devfeed.tech/tags/http.md>), [performance](<https://devfeed.tech/tags/performance.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [stream](<https://devfeed.tech/tags/stream.md>), [token](<https://devfeed.tech/tags/token.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [websockets](<https://devfeed.tech/tags/websockets.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Workflow SDK 5.2.0 and later sends event and stream writes to Vercel Workflows over a WebSocket by default, reducing HTTP requests. Upgrading and deploying is sufficient; new runs use the deployed version, while in-flight runs finish on their starting deployment. Existing streaming code continues to work, and bursts of chunks are sent once the connection opens. In a benchmark replaying an AI agent's token stream, v5.2.0 delivered the full response 4.2x faster than v4.8.12, with no chunk delayed over a second. Step start and completion writes also use the connection, which the source says reduces requests and can improve performance and costs. The queue handler opens a connection for each delivery. Users upgrading from 4.x should follow the major-version upgrade guide.

### Source excerpt

The Workflow SDK now sends event writes and stream writes to Vercel Workflows over a WebSocket by default, replacing one HTTP request per write, or per write group for streams. No code change is needed beyond upgrading to workflow@5.2.0 or later. Once you deploy the upgrade, new runs use it. In-flight runs finish on the deployment they started on. Existing streaming code works as is. A step that writes a burst of chunks, like AI tokens, sends them over the WebSocket once it opens: Streams keep pace with AI output In a benchmark replaying an AI agent's token stream, v5.2.0, which writes streams over a WebSocket by default, delivered the full response 4.2x faster than v4.8.12, with no chunk delayed over a second. Fewer HTTP requests for event writes Every step start and completion is an event write, now sent over the WebSocket, so workflows with many steps make fewer HTTP requests. The added efficiency also improves performance and reduces costs. The queue handler opens the connection for every delivery. Get started Read the Vercel World documentation to get started. If you're on 4.x, start with the upgrade guide, since v5 is a major release. Read more

## Preview web apps live as your coding agent builds them with Amazon Bedrock AgentCore runtime

DevFeed: [Preview web apps live as your coding agent builds them with Amazon Bedrock AgentCore runtime](<https://devfeed.tech/articles/preview-web-apps-live-as-your-coding-agent-builds-them-with-amazon-bedrock-agentcore-runtime-109415.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/preview-web-apps-live-as-your-coding-agent-builds-them-with-amazon-bedrock-agentcore-runtime/>)

Author: Sundar Raghavan

Published: 2026-10-30T21:40:03Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [browser](<https://devfeed.tech/tags/browser.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [files](<https://devfeed.tech/tags/files.md>), [http](<https://devfeed.tech/tags/http.md>), [live](<https://devfeed.tech/tags/live.md>), [preview](<https://devfeed.tech/tags/preview.md>), [running](<https://devfeed.tech/tags/running.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [update](<https://devfeed.tech/tags/update.md>), [url](<https://devfeed.tech/tags/url.md>), [vite](<https://devfeed.tech/tags/vite.md>), [web-apps](<https://devfeed.tech/tags/web-apps.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

AgentCore Session endpoints let you preview a web app running inside the same isolated runtime session where a coding agent edits it. The walkthrough runs a Vite site on port 8090 and an agent on port 8080; an authenticated local endpoint forwards browser HTTP and WebSocket traffic to allowed session ports, while prompts reach the agent through InvokeAgentRuntime. Vite hot reload then shows saved changes without a page refresh. Session endpoint access requires SigV4 for IAM runtimes or a bearer token for JWT-authorized runtimes, and URLs work only for the session's lifetime. The sample requires a microVM runtime, configured AWS permissions and credentials, Python and Node.js dependencies, and Claude Haiku 5.5 access; it uses direct Node.js code deployment without Docker or ECR. Session endpoints support HTTP/1.1, HTTP/2, and WebSockets, but do not support inbound AWS PrivateLink. The text also notes that agent and site share a session, so role permissions should be limited and edits may not survive replacement compute without persistent storage.

### Source excerpt

Amazon Bedrock AgentCore Session endpoints give each runtime session an authenticated URL that forwards any HTTP method, path, and WebSocket connection to the ports you allow. In this post, you deploy a coding agent that keeps a Vite website running in its session, then watch the live site update in your browser as the agent edits files.

## CVE-2026-118264 - Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls

DevFeed: [CVE-2026-118264 - Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls](<https://devfeed.tech/articles/cve-2026-118264-echo-rejected-websocket-upgrades-can-bypass-echo-route-level-access-controls-105485.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-118264>)

Author: CVEFEED.io; github.com

Published: 2026-10-28T19:17:31Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [backend frameworks](<https://devfeed.tech/topics/backend-frameworks.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [client](<https://devfeed.tech/tags/client.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-118264](<https://devfeed.tech/tags/cve-2026-118264.md>), [echo](<https://devfeed.tech/tags/echo.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [go](<https://devfeed.tech/tags/go.md>), [http](<https://devfeed.tech/tags/http.md>), [independent](<https://devfeed.tech/tags/independent.md>), [issue](<https://devfeed.tech/tags/issue.md>), [keep](<https://devfeed.tech/tags/keep.md>), [labstack](<https://devfeed.tech/tags/labstack.md>), [route](<https://devfeed.tech/tags/route.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

In affected Echo versions from 4.0.0 up to 4.16.1 and 5.4.1, Proxy middleware can select a raw tunnel from a client WebSocket upgrade request before confirming the upstream accepted it. If the upstream responds with an ordinary keep-alive response, later HTTP requests on that connection go directly to the upstream, bypassing Echo routing and route-level middleware. This can evade authentication or authorization enforced only by Echo when the proxy route is accessible, the upstream cooperates by rejecting the upgrade this way, and the target has no independent authorization. The issue is fixed in Echo 4.16.1 and 5.4.1.

### Source excerpt

CVE ID :CVE-2026-118264 Published : Oct. 28, 2026, 7:17 p.m. | 2 hours ago Description :Echo is a Go web framework. From 4.0.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware selects a raw tunnel from a client WebSocket upgrade request before verifying that the configured upstream accepted the upgrade. If the upstream rejects the upgrade with an ordinary keep-alive response, later HTTP requests on the connection are sent directly to that upstream without passing through Echo's router or route-specific middleware. This can bypass authentication or authorization enforced only by Echo routes, but requires an accessible proxy route, a cooperating rejected-upgrade response, and a target without independent upstream authorization. This issue is fixed in 4.16.1 and 5.4.1. Severity: 9.1 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-118262 - Echo: WebSocket proxy can retain connections and handlers after client disconnect

DevFeed: [CVE-2026-118262 - Echo: WebSocket proxy can retain connections and handlers after client disconnect](<https://devfeed.tech/articles/cve-2026-118262-echo-websocket-proxy-can-retain-connections-and-handlers-after-client-disconnect-105484.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-118262>)

Author: CVEFEED.io; github.com

Published: 2026-10-28T19:17:30Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve-2026-118262](<https://devfeed.tech/tags/cve-2026-118262.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [echo](<https://devfeed.tech/tags/echo.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [go](<https://devfeed.tech/tags/go.md>), [goroutines](<https://devfeed.tech/tags/goroutines.md>), [handler](<https://devfeed.tech/tags/handler.md>), [http](<https://devfeed.tech/tags/http.md>), [labstack](<https://devfeed.tech/tags/labstack.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [network](<https://devfeed.tech/tags/network.md>), [peer](<https://devfeed.tech/tags/peer.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

Echo versions 4.15.0 through before 4.16.1, and 5.4.1, can retain handlers, copy goroutines, and network connections after a WebSocket client disconnects if the upstream keeps its connection open. The raw proxy waits for both data-copy directions and may not close the peer connection when one direction ends; this can also occur with an HTTP keep-alive response that rejects an upgrade. Repeated connections can accumulate resources and cause denial of service, depending on proxy-route accessibility, upstream behavior, and connection deadlines. The issue is fixed in Echo 4.16.1 and 5.4.1.

### Source excerpt

CVE ID :CVE-2026-118262 Published : Oct. 28, 2026, 7:17 p.m. | 2 hours ago Description :Echo is a Go web framework. From 4.15.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware can retain a handler, copy goroutines, and network connections after a WebSocket client disconnects when the upstream keeps its connection open. The raw proxy waits for both copy directions without reliably closing the peer connection when one direction ends, including when a rejected upgrade response uses HTTP keep-alive. Repeated connections can accumulate resources and cause denial of service, depending on proxy-route accessibility, upstream behavior, and connection deadlines. This issue is fixed in 4.16.1 and 5.4.1. Severity: 8.2 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Deploy Blazor Server applications on Amazon ECS with AWS Fargate

DevFeed: [Deploy Blazor Server applications on Amazon ECS with AWS Fargate](<https://devfeed.tech/articles/deploy-blazor-server-applications-on-amazon-ecs-with-aws-fargate-102778.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/dotnet/deploy-blazor-server-applications-on-amazon-ecs-with-aws-fargate/>)

Author: Mayank Kumar

Published: 2026-10-27T10:30:08Z

Content type: article

Language: en

Sources: [.NET on AWS Blog](<https://devfeed.tech/sources/net-on-aws-blog.md>)

Topics: [AWS Fargate](<https://devfeed.tech/topics/aws-fargate.md>), [Blazor](<https://devfeed.tech/topics/blazor.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [SignalR](<https://devfeed.tech/topics/signalr.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>)

Tags: [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [applications](<https://devfeed.tech/tags/applications.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-development-kit](<https://devfeed.tech/tags/aws-cloud-development-kit.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [blazor](<https://devfeed.tech/tags/blazor.md>), [circuit](<https://devfeed.tech/tags/circuit.md>), [component](<https://devfeed.tech/tags/component.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [forms](<https://devfeed.tech/tags/forms.md>), [framework](<https://devfeed.tech/tags/framework.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [memory](<https://devfeed.tech/tags/memory.md>), [model](<https://devfeed.tech/tags/model.md>), [modernizing](<https://devfeed.tech/tags/modernizing.md>), [net](<https://devfeed.tech/tags/net.md>), [programming](<https://devfeed.tech/tags/programming.md>), [server](<https://devfeed.tech/tags/server.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

Blazor Server circuits live in one process's memory, so ECS deployments must preserve task affinity and WebSocket connectivity while treating circuits as disposable. The described AWS CDK for C# setup places Fargate tasks behind an internal Application Load Balancer reached through CloudFront VPC origin; target group cookies keep a browser on one task, and CloudFront disables caching and forwards viewer data for application traffic while separate behaviors cache static assets. It aligns SignalR keep-alives (15 seconds), long-poll timeout (45 seconds), and CloudFront and load balancer limits (60 seconds), and uses a 60-second deregistration delay for in-flight requests. Replaced tasks still disconnect circuits, so persistent session data must live outside them, such as in RDS PostgreSQL, ElastiCache Redis, or device-local browser storage, and be rehydrated after reconnect. The sample uses a single Availability Zone to reduce cost and calls for multi-zone deployment in production; its 1 GiB task is sample-sized and should be sized from workload measurements. Shared Data Protection keys via Systems Manager require task permissions and network access to an SSM endpoint.

### Source excerpt

When modernizing legacy ASP.NET Web Forms applications with tools such as AWS Transform, Blazor Server is often recommended as the target framework. With Blazor, you gain a familiar component-based programming model - but you also inherit a deployment challenge. Blazor Server maintains a persistent WebSocket connection and an in-memory circuit for each browser session, which [...]

## The Night Before the Demo, My AI Drive-Thru Started to Stutter

DevFeed: [The Night Before the Demo, My AI Drive-Thru Started to Stutter](<https://devfeed.tech/articles/the-night-before-the-demo-my-ai-drive-thru-started-to-stutter-100951.md>)

Original publisher: [Read original article](<https://proandroiddev.com/building-an-ai-drive-thru-agent-in-flutter-ec3953087ffd?source=rss----c72404660798---4>)

Author: Akashshahriar

Published: 2026-10-26T23:26:05Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [speech-to-speech](<https://devfeed.tech/topics/speech-to-speech.md>), [asr](<https://devfeed.tech/topics/asr.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [audio](<https://devfeed.tech/tags/audio.md>), [brain](<https://devfeed.tech/tags/brain.md>), [can](<https://devfeed.tech/tags/can.md>), [car](<https://devfeed.tech/tags/car.md>), [card](<https://devfeed.tech/tags/card.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [code](<https://devfeed.tech/tags/code.md>), [counter](<https://devfeed.tech/tags/counter.md>), [deepgram](<https://devfeed.tech/tags/deepgram.md>), [echo](<https://devfeed.tech/tags/echo.md>), [engine](<https://devfeed.tech/tags/engine.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [full](<https://devfeed.tech/tags/full.md>), [headset](<https://devfeed.tech/tags/headset.md>), [i](<https://devfeed.tech/tags/i.md>), [inside](<https://devfeed.tech/tags/inside.md>), [job](<https://devfeed.tech/tags/job.md>), [just](<https://devfeed.tech/tags/just.md>), [voice-assistant](<https://devfeed.tech/tags/voice-assistant.md>)

### AI overview

The kiosk's menu and cart stayed reliable with a small OpenAI model calling guarded Dart tools, while the hardest problem was audio on the actual Android tablet. Deepgram streaming transcription used tuned pause thresholds, selective menu hints and interim text as a fallback; code enforced stock, quantity and checkout limits, and kept the live cart authoritative. Full-duplex audio worked in development, but the tablet's hardware echo-cancellation output path made speech stutter, and larger buffers added too much delay. The author shipped half-duplex instead, pausing the mic during speech; writing 20 ms of silence into an empty playback buffer kept the track awake and reduced startup buffering to about 250 ms. Checkout remained in the existing kiosk flow after spoken confirmation. The account recommends testing on the real device early; software echo cancellation is a possible next step, with playback-to-microphone delay alignment still unresolved.

### Source excerpt

Deepgram for ears, a small LLM with tools for the brain, a native audio engine for the mouth. How a kiosk takes a full order by voice, and why the echo canceller lost. You know this one. You pull up to the drive-thru speaker. It crackles. "Welcome, what can I get you?" You order a burger, no onions, a large fries and a Coke. Silence. Then: "Sorry, can you repeat that?" You repeat it, louder, leaning out of the window. Behind you a car honks. At the window they hand you a bag with onions in it and no fries. Nobody in that story did anything wrong. The person on the headset is also bagging orders, watching a timer and taking a second lane. The speaker is cheap, the lane is noisy, and the job is to understand fifty strangers an hour through both. Now the other version. You walk up to a kiosk and just talk to it, the way you would talk to a person. "The classic Smashburger. Actually, make it two. And a medium Coke." It answers in a second. It knows the menu, knows what is sold out, never forgets the "no onions", never gets tired at the end of a shift, and reads the order back before it takes your card. You tap, a receipt prints, you leave. Every restaurant chain wants that second version. Some have already tried it in public and pulled it after videos of the AI adding hundreds of nuggets to one order went viral. It is harder than it looks. I built one. A Flutter kiosk that greets you, takes the whole order by voice, reads it back, sends you to the card terminal and prints the receipt. No screen taps until the card. This is how it works, what nearly broke it the day before it ran live, and why the simple version won. What is inside Three parts, the same three you would use to describe a person at the counter: Ears. Deepgram, streaming speech to text over a WebSocket. Brain. A small OpenAI model (gpt-5.4-mini) with tools for the menu, the cart and checkout. Mouth. A native audio plugin that owns the microphone and the speaker. The code below is rewritten and trimmed. The

## How Trax keeps aircraft maintenance real-time with Quarkus

DevFeed: [How Trax keeps aircraft maintenance real-time with Quarkus](<https://devfeed.tech/articles/how-trax-keeps-aircraft-maintenance-real-time-with-quarkus-101133.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/trax-real-time-aircraft-maintenance-with-quarkus/>)

Author: Emil Lefkof

Published: 2026-10-26T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [real-time](<https://devfeed.tech/topics/real-time.md>)

Tags: [aircraft](<https://devfeed.tech/tags/aircraft.md>), [airlines](<https://devfeed.tech/tags/airlines.md>), [batch](<https://devfeed.tech/tags/batch.md>), [changes](<https://devfeed.tech/tags/changes.md>), [control](<https://devfeed.tech/tags/control.md>), [controller](<https://devfeed.tech/tags/controller.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [desktop-application](<https://devfeed.tech/tags/desktop-application.md>), [erp](<https://devfeed.tech/tags/erp.md>), [event](<https://devfeed.tech/tags/event.md>), [flight](<https://devfeed.tech/tags/flight.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ipad](<https://devfeed.tech/tags/ipad.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [real-time](<https://devfeed.tech/tags/real-time.md>)

### AI overview

Trax's eMobility suite uses Quarkus to keep maintenance controllers' React dashboards and mechanics' iOS apps current while Oracle remains the shared system of record. Debezium reads Oracle redo logs and publishes changes to Kafka; Quarkus Kafka Streams handlers refresh caches and send compact invalidation messages over WebSockets, so clients re-fetch only affected data. Each pod uses its stable, unique HOSTNAME in the Kafka Streams application ID: separate consumer groups let every pod receive each event, while stability lets a restarted pod resume its group. Since CDC can emit many records for one action or batch, updates are coalesced by record identity and flushed after a shared one-second trailing delay. Foreground clients use WebSockets; backgrounded iPads receive APNs notifications. OpenAPI is generated and committed so Swift and React clients can be generated from one contract and catch API changes at build time. The account is an implementation overview; it does not report measured delivery latency or reliability.

### Source excerpt

Quarkus turns up in places most people never think to look for it. This one lives on the ramp, in the hangar, and in the hands of the mechanic standing under a wing at 3am. A short background on Trax Trax builds MRO software -- Maintenance, Repair and Overhaul -- for airlines, cargo operators and independent maintenance providers. If an aircraft is being worked on, something has to track it: the work orders, the task cards, the parts consumed, the sign-offs, the airworthiness records that a regulator can ask to see years later. Trax has been doing that for over 25 years, and today its systems cover thousands of aircraft for customers across dozens of countries. Historically this was a heavyweight desktop application backed by a very large Oracle database. The modern push is paperless maintenance: get the mechanic off the clipboard and onto an iPad at the aircraft, and give the maintenance controller a live web dashboard instead of a report that was true ten minutes ago. That product line is called eMobility, and the technology behind it is a suite of Quarkus applications. The problem These services have to serve two very different front ends: A React web application used by maintenance control and line control staff on desktops. A Swift/SwiftUI iOS application used by mechanics on iPads out at the aircraft. Both need the same data, and both need it to be current. When a work order changes status, when a flight's maintenance crew assignment moves, when a defect is raised against an aircraft, every connected client should know within seconds -- without hammering the database with polling. The wrinkle is that the system of record is the existing Oracle ERP database, and a great deal of what writes to it is not our service. Other Trax applications, batch jobs, and integrations all write to the same tables. We cannot simply fire an event from our own code after a transaction commits, because most of the interesting changes do not originate in our code at all. So the require

## battledrones v14: Compass Rose, a four player map

DevFeed: [battledrones v14: Compass Rose, a four player map](<https://devfeed.tech/articles/battledrones-v14-compass-rose-a-four-player-map-98867.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Oct/24/battledrones/>)

Author: Simon Willison

Published: 2026-10-24T03:59:57Z

Content type: release

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [multiplayer](<https://devfeed.tech/topics/multiplayer.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-321](<https://devfeed.tech/tags/claude-321.md>), [colors](<https://devfeed.tech/tags/colors.md>), [game-design](<https://devfeed.tech/tags/game-design.md>), [game-design-28](<https://devfeed.tech/tags/game-design-28.md>), [green](<https://devfeed.tech/tags/green.md>), [map](<https://devfeed.tech/tags/map.md>), [model](<https://devfeed.tech/tags/model.md>), [multiplayer](<https://devfeed.tech/tags/multiplayer.md>), [network](<https://devfeed.tech/tags/network.md>), [online](<https://devfeed.tech/tags/online.md>), [preview](<https://devfeed.tech/tags/preview.md>), [projects](<https://devfeed.tech/tags/projects.md>), [projects-561](<https://devfeed.tech/tags/projects-561.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [qr-codes](<https://devfeed.tech/tags/qr-codes.md>), [robots](<https://devfeed.tech/tags/robots.md>), [share](<https://devfeed.tech/tags/share.md>), [symmetry](<https://devfeed.tech/tags/symmetry.md>), [teams](<https://devfeed.tech/tags/teams.md>), [units](<https://devfeed.tech/tags/units.md>), [use-ai](<https://devfeed.tech/tags/use-ai.md>), [websocket](<https://devfeed.tech/tags/websocket.md>), [websockets](<https://devfeed.tech/tags/websockets.md>)

### AI overview

Battledrones v14 adds Compass Rose, a four-player map with four-way rotational symmetry, and extends WebSocket multiplayer on that map to support up to four human players. Players can join via share links or QR codes; any unfilled slots use AI. The update also adds purple and green robot teams alongside the existing blue and red, with their colors previewable in the model browser. The excerpt mentions a replay of a four-way AI battle using the Goliath Armada mutator, which gives each side four giant Goliath mechs.

### Source excerpt

Release: battledrones v14: Compass Rose, a four player map I added four player online mode to Battledrones - previous maps were limited to two. Here's the initial prompt I used: Add a new map for a four player battle - four way rotational symmetry, up to four AI players, works with the WebSocket non-audio based multiplayer mode so up to four human players can join (any spare slots use AI) Claude Opus 4.5 added a new map called "Compass Rose" and modified the WebSockets multiplayer network code to support up to four players for that map, joining via share links or QR codes. The new teams use robots themed in purple and green, joining the existing blue and red designs. You can preview those colors in the updated model browser. Here's a replay link to watch a four way AI battle with the "Goliath Armada" mutator turned on, where each side starts with four giant Goliath mech units. Tags: game-design, projects, claude

## CVE-2026-46651 - Unauthenticated SSRF and local file inclusion via DownloadTaskEndpoint WebSocket in Goobi viewer

DevFeed: [CVE-2026-46651 - Unauthenticated SSRF and local file inclusion via DownloadTaskEndpoint WebSocket in Goobi viewer](<https://devfeed.tech/articles/cve-2026-46651-unauthenticated-ssrf-and-local-file-inclusion-via-downloadtaskendpoint-websocket-in-goobi-viewer-98319.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-46651>)

Author: CVEFEED.io; github.com

Published: 2026-10-23T15:17:31Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-46651](<https://devfeed.tech/tags/cve-2026-46651.md>), [download](<https://devfeed.tech/tags/download.md>), [goobi-viewer-core](<https://devfeed.tech/tags/goobi-viewer-core.md>), [intranda](<https://devfeed.tech/tags/intranda.md>), [local-file-inclusion](<https://devfeed.tech/tags/local-file-inclusion.md>), [ssrf](<https://devfeed.tech/tags/ssrf.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

Goobi viewer versions 24.03 through releases before 26.05 accept unauthenticated download requests through goobi-viewer-core's DownloadTaskEndpoint WebSocket endpoint at /tasks/download/monitor.socket. The issue is described as enabling SSRF and local file inclusion. It is patched in version 26.05.

### Source excerpt

CVE ID :CVE-2026-46651 Published : Oct. 23, 2026, 3:17 p.m. | 4 hours, 25 minutes ago Description :The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. From version 24.03 to before version 26.05, the DownloadTaskEndpoint WebSocket endpoint (/tasks/download/monitor.socket) in goobi-viewer-core accepts download requests from unauthenticated users. This issue has been patched in version 26.05. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Agent Graph Engineering, Part 3: Why Your WebSocket Clients Need Generated Types

DevFeed: [Agent Graph Engineering, Part 3: Why Your WebSocket Clients Need Generated Types](<https://devfeed.tech/articles/agent-graph-engineering-part-3-why-your-websocket-clients-need-generated-types-95272.md>)

Original publisher: [Read original article](<https://hackernoon.com/agent-graph-engineering-part-3-why-your-websocket-clients-need-generated-types?source=rss>)

Author: Huy Nguyen

Published: 2026-10-22T08:21:23Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [union types](<https://devfeed.tech/topics/union-types.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-safety](<https://devfeed.tech/tags/ai-agent-safety.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backend-development](<https://devfeed.tech/tags/backend-development.md>), [cross-language-types](<https://devfeed.tech/tags/cross-language-types.md>), [graph](<https://devfeed.tech/tags/graph.md>), [python](<https://devfeed.tech/tags/python.md>), [services](<https://devfeed.tech/tags/services.md>), [types](<https://devfeed.tech/tags/types.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

The article argues that when services cross process or language boundaries, declare data shapes on the server and generate clients and interfaces from those contracts. OpenAPI supplies a typed REST client; AsyncAPI carries WebSocket event types and directionality into TypeScript, so adding or removing an event updates the generated union and can expose stale frontend handling at compile time. Tool argument schemas can also drive approval forms, validation, and defaults, helping ensure reviewers see the fields the server accepts. The approach adds build and regeneration steps, may require a live schema endpoint, and inherits generator choices; the article says it brings little value for one service in one language or throwaway prototypes, while public APIs still need versioning.

### Source excerpt

Three services in two languages means three seams, and a hand-maintained seam is a slow leak.

## Respan spent two years building on LiteLLM. One upgrade made it start over.

DevFeed: [Respan spent two years building on LiteLLM. One upgrade made it start over.](<https://devfeed.tech/articles/respan-spent-two-years-building-on-litellm-one-upgrade-made-it-start-over-91304.md>)

Original publisher: [Read original article](<https://thenewstack.io/respan-rust-ai-gateway/>)

Author: Amanda Caswell

Published: 2026-10-20T22:13:08Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [litellm](<https://devfeed.tech/topics/litellm.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [litellm](<https://devfeed.tech/tags/litellm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rust](<https://devfeed.tech/tags/rust.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Respan replaced a 100,000-line LiteLLM wrapper, after an unexplained January 2026 upgrade caused intermittent connection failures, with a pre-alpha Rust gateway built around a small core and plugins. Plugins can route requests, select providers, transform responses, make calls, or stop requests; protocol translation can let an OpenAI Realtime client connect to Gemini Live, though some features may not carry over. Provider-specific quirks can be isolated, and same-format requests can retain provider fields. Custom plugins must be compiled into the gateway, requiring code maintenance and rebuilds; they run in-process with access to sensitive request data, and their registration order matters--a cache before a security check could bypass it. In contrast, LiteLLM is porting routes incrementally, with Rust off by default and unsupported requests falling back to Python. LiteLLM's claimed performance comparisons are from its own benchmark tests. Respan says its binary can be run without its paid platform.

### Source excerpt

Respan released an open-source AI gateway written in Rust on Tuesday, after spending two years building more than 100,000 lines The post Respan spent two years building on LiteLLM. One upgrade made it start over. appeared first on The New Stack.

## WebSocket support is now generally available

DevFeed: [WebSocket support is now generally available](<https://devfeed.tech/articles/websocket-support-is-now-generally-available-91280.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/websocket-support-is-now-generally-available>)

Author: Matthew Stanciu

Published: 2026-10-20T20:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [multiplayer](<https://devfeed.tech/topics/multiplayer.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-chat](<https://devfeed.tech/tags/ai-chat.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [beta](<https://devfeed.tech/tags/beta.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [functions](<https://devfeed.tech/tags/functions.md>), [messages](<https://devfeed.tech/tags/messages.md>), [models](<https://devfeed.tech/tags/models.md>), [multiplayer](<https://devfeed.tech/tags/multiplayer.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [processing](<https://devfeed.tech/tags/processing.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

WebSocket support in Vercel Functions is generally available. Since the public beta began in late June, Vercel CDN has served 300 million WebSocket connections and now serves 15 million per day. The excerpt names AI chat, streaming, and realtime multiplayer apps as customer use cases, and says WebSockets power AI Gateway's realtime models. Connections follow the same limits and pricing as other Function invocations; with Active CPU pricing, CPU is billed only while messages are being processed.

### Source excerpt

WebSocket support in Vercel Functions is now generally available. Since the public beta launched in late June, Vercel CDN has served 300 million WebSocket connections, and now serves 15 million per day. Customers use WebSockets for AI chat, streaming, and realtime multiplayer apps. WebSockets also power AI Gateway's realtime models. WebSocket connections follow the same limits and pricing as other Function invocations. With Active CPU pricing, CPU is billed only for the time spent processing messages. Get started at the documentation. Read more

## Intro to WebSocket Streaming with Runpod Serverless

DevFeed: [Intro to WebSocket Streaming with Runpod Serverless](<https://devfeed.tech/articles/intro-to-websocket-streaming-with-runpod-serverless-91128.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/websocket-streaming-runpod-serverless>)

Author: Brendan McKeag

Published: 2026-10-20T18:19:28Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [api-key](<https://devfeed.tech/tags/api-key.md>), [base64](<https://devfeed.tech/tags/base64.md>), [client](<https://devfeed.tech/tags/client.md>), [development-environment](<https://devfeed.tech/tags/development-environment.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [dockerhub](<https://devfeed.tech/tags/dockerhub.md>), [files](<https://devfeed.tech/tags/files.md>), [image-processing](<https://devfeed.tech/tags/image-processing.md>), [json](<https://devfeed.tech/tags/json.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

The tutorial demonstrates a Runpod Serverless endpoint that accepts files encoded as base64 in a JSON payload and streams results back over WebSocket. It describes creating a handler, Dockerfile, and requirements.txt, building and pushing the image to DockerHub, then configuring an endpoint. A test script uses a Runpod API key and Endpoint ID to submit a request and save the returned base64 JSON payload locally. The example simulates image processing by producing a blank image; the excerpt says the pattern can be extended to other file-processing tasks.

### Source excerpt

This follow-up to our "Hello World" tutorial walks through streaming output from a Runpod Serverless endpoint using WebSocket and base64 files.

## Kubernetes Development Updates: WebSocket Streaming Metrics Advance to Beta

DevFeed: [Kubernetes Development Updates: WebSocket Streaming Metrics Advance to Beta](<https://devfeed.tech/articles/week-ending-october-11-2026-88408.md>)

Original publisher: [Read original article](<https://lwkd.info/2026/20261015>)

Published: 2026-10-15T23:45:00Z

Content type: news

Language: en

Sources: [Last Week in Kubernetes Development](<https://devfeed.tech/sources/last-week-in-kubernetes-development.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>)

Tags: [developer-news](<https://devfeed.tech/tags/developer-news.md>), [dra](<https://devfeed.tech/tags/dra.md>)

### AI overview

Kubernetes development updates cover WebSocket tests that prevent fallback to SPDY, streaming metrics advancing to Beta, and more precise Job failure reasons. The roundup also explains optional device preparation and cleanup operations in Dynamic Resource Allocation and reports release deadlines and contributor events.

### Source excerpt

Developer News

## Multi-region disaster recovery for Amazon API Gateway WebSocket APIs

DevFeed: [Multi-region disaster recovery for Amazon API Gateway WebSocket APIs](<https://devfeed.tech/articles/multi-region-disaster-recovery-for-amazon-api-gateway-websocket-apis-87253.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/multi-region-disaster-recovery-for-amazon-api-gateway-websocket-apis/>)

Author: Shubham Dhoka

Published: 2026-10-14T14:31:55Z

Content type: tutorial

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [treeherder](<https://devfeed.tech/topics/treeherder.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [failover](<https://devfeed.tech/tags/failover.md>), [health](<https://devfeed.tech/tags/health.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

This tutorial presents an active-passive, multi-region disaster recovery pattern for Amazon API Gateway WebSocket applications. It combines Route 53 DNS failover, DynamoDB Global Tables for replicated state, a canary health probe, and client reconnection logic so sessions can recover after a regional outage. The article also discusses asynchronous replication limits, health-check thresholds, and backoff with jitter.

### Source excerpt

Learn how to build multi-region disaster recovery for Amazon API Gateway WebSocket APIs. This design pattern combines Amazon Route 53 DNS failover, Amazon DynamoDB Global Tables, a canary health probe, and client-side reconnection logic to reconnect clients and restore session state automatically during a regional failover.

## Exploring AWS Lambda Web Functions for building web applications

DevFeed: [Exploring AWS Lambda Web Functions for building web applications](<https://devfeed.tech/articles/exploring-aws-lambda-web-functions-for-building-web-applications-86349.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/exploring-aws-lambda-web-functions-for-building-web-applications/>)

Author: Julian Wood

Published: 2026-10-13T17:59:52Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Node.js](<https://devfeed.tech/topics/node-js.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [cost](<https://devfeed.tech/tags/cost.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [web-server](<https://devfeed.tech/tags/web-server.md>)

### AI overview

A walkthrough of AWS Lambda Web Functions shows how to deploy a standard Node.js HTTP server, handle concurrent requests, scale across execution environments and Regions, and configure authentication. It also explains active-CPU billing and demonstrates the service with a live metrics dashboard.

### Source excerpt

Run a standard Node.js web server on AWS Lambda with Lambda Web Functions, a new type of Lambda function. Deploy it with one command or AWS CloudFormation and get a public HTTPS endpoint with no adapter layer and no servers to manage. See how one execution environment handles many concurrent requests and how active-CPU billing keeps the cost of waiting low.

## Tips and Tricks for Using TanStack Start with Cloudflare Durable Objects

DevFeed: [Tips and Tricks for Using TanStack Start with Cloudflare Durable Objects](<https://devfeed.tech/articles/tips-and-tricks-for-using-tanstack-start-with-cloudflare-durable-objects-85318.md>)

Original publisher: [Read original article](<https://blog.master.dev/tips-and-tricks-for-using-tanstack-start-with-cloudflare-durable-objects/>)

Author: Adam Rackis

Published: 2026-10-12T12:56:15Z

Content type: tutorial

Language: en

Sources: [Master.dev Blog RSS Feed](<https://devfeed.tech/sources/master-dev-blog-rss-feed.md>)

Topics: [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Socket.IO](<https://devfeed.tech/topics/socket-io.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [durable-objects](<https://devfeed.tech/tags/durable-objects.md>), [tanstack](<https://devfeed.tech/tags/tanstack.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

The article shares practical tips for combining TanStack Start with Cloudflare Durable Objects. It demonstrates middleware for making Durable Object instances available to server functions, tagged WebSocket connections for routing messages to relevant sessions, and an explicit return type to address a TypeScript serialization error involving the Disposable type.

### Source excerpt

Some hot tips on using middleware for simplifying Durable Object creation and managing WebSocket connections.

## NGINX Explained: 8 Use Cases Every Developer Should Know

DevFeed: [NGINX Explained: 8 Use Cases Every Developer Should Know](<https://devfeed.tech/articles/nginx-explained-8-use-cases-every-developer-should-know-85194.md>)

Original publisher: [Read original article](<https://blog.levelupcoding.com/p/nginx-explained-top-8-use-cases>)

Author: Nikki Siapno

Published: 2026-10-12T11:46:46Z

Content type: tutorial

Language: en

Sources: [Level Up Coding System Design Newsletter](<https://devfeed.tech/sources/level-up-coding-system-design-newsletter.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [least connections](<https://devfeed.tech/topics/least-connections.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [allows](<https://devfeed.tech/tags/allows.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [application-servers](<https://devfeed.tech/tags/application-servers.md>), [browser](<https://devfeed.tech/tags/browser.md>), [business](<https://devfeed.tech/tags/business.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-stampede](<https://devfeed.tech/tags/cache-stampede.md>), [caching](<https://devfeed.tech/tags/caching.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-management](<https://devfeed.tech/tags/certificate-management.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [server](<https://devfeed.tech/tags/server.md>), [web](<https://devfeed.tech/tags/web.md>), [web-server](<https://devfeed.tech/tags/web-server.md>)

### AI overview

A practical overview of eight NGINX roles at the edge: reverse proxying, load balancing, static file serving, TLS termination, caching, rate limiting, request routing, and WebSocket proxying. It explains how these functions affect application capacity and where traffic configuration should remain separate from application business logic.

### Source excerpt

Calling NGINX a web server isn't wrong. It just describes one of its jobs...

## WebSocket servers in JavaScript: Node.js, Bun and Deno in 2026

DevFeed: [WebSocket servers in JavaScript: Node.js, Bun and Deno in 2026](<https://devfeed.tech/articles/websocket-servers-in-javascript-node-js-bun-and-deno-in-2026-84487.md>)

Original publisher: [Read original article](<https://lemire.me/blog/2026/10/10/websocket-servers-in-javascript-node-js-bun-and-deno-in-2026/>)

Author: Daniel Lemire

Published: 2026-10-10T08:56:11Z

Content type: comparison

Language: en

Sources: [Daniel Lemire](<https://devfeed.tech/sources/daniel-lemire.md>)

Topics: [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [Deno](<https://devfeed.tech/topics/deno.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [deno](<https://devfeed.tech/tags/deno.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

This benchmark compares WebSocket server performance using Node.js with uWebSockets.js, Bun's built-in server, and Deno's built-in server. In a single-core ping-pong test with C clients, Node.js reached 49,000 round trips per second, compared with 40,000 for Deno and 37,000 for Bun; the reported 99th-percentile times were 24.8, 32.0, and 46.4 microseconds, respectively.

### Source excerpt

WebSocket is a standard protocol to hook up a client and a server in a persistent manner. It is commonly used for live chat, notifications, multiplayer games, collaborative editing, and streaming dashboards. Many servers are written in JavaScript and use Node.js, Bun or Deno as an engine. A few years ago, I wrote a simple ... Continue reading WebSocket servers in JavaScript: Node.js, Bun and Deno in 2026

## Telegraf Socket Listener Plugin: UDP, TCP and Unix Sockets

DevFeed: [Telegraf Socket Listener Plugin: UDP, TCP and Unix Sockets](<https://devfeed.tech/articles/telegraf-socket-listener-plugin-udp-tcp-and-unix-sockets-88341.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-socket-listener-input-plugin/>)

Author: Noah Crowley (InfluxData)

Published: 2026-10-09T07:00:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Website](<https://devfeed.tech/topics/website.md>), [TCP/IP](<https://devfeed.tech/topics/tcp-ip.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [product](<https://devfeed.tech/tags/product.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [udp](<https://devfeed.tech/tags/udp.md>), [unix](<https://devfeed.tech/tags/unix.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

The article shows how to use Telegraf's socket_listener input plugin to send data into Telegraf and InfluxDB over UDP and Unix sockets. It explains UDP's delivery and overhead tradeoffs, configures a UDP listener on port 8094, and demonstrates sending and verifying points. It then shows a Python script that writes random walk data through a Unix datagram socket, noting that Unix sockets can reduce local communication overhead.

### Source excerpt

One of Telegraf's biggest strengths is the large collection of plugins it offers that can be used to immediately start collecting data from a variety of applications. This covers a lot of common infrastructure components like databases and web servers, but if you want to get data into Telegraf using your own scripts or applications, there are also a variety of more general-purpose input plugins that you can use. There's a file plugin, which will read from or tail a file on disk, an exec plugin which will execute your own scripts or commands and parse their output, and plugins to listen for data via HTTP or poll external endpoints (http_listener_v2 and http). One of the plugins I end up using most often is the socket_listener plugin, which allows you to send data to Telegraf using UDP, TCP, or Unix sockets. The simplicity of InfluxDB's line protocol and the ease with which you can write to a socket using most programming languages makes this a powerful tool for both quick prototyping and more long-term solutions. Let's take a look at some examples of the plugin in action. We'll use a host system running Ubuntu, with Telegraf and InfluxDB installed from the official InfluxData repository. UDP: User Datagram Protocol For this first example, let's configure the socket_listener plugin to accept UDP packets. The UDP protocol is a connectionless, best-effort service: messages are sent to their recipient with no guarantee that they will be received. One benefit of this is that it means there is less processing overhead for UDP relative to something like TCP, which is more reliable. That makes UDP well-suited for things like interprocess communication or situations in which some loss of data is acceptable. In order to set up Telegraf to receive UDP messages, first configure this block in your telegraf.conf: [[inputs.socket_listener]] service_address = "udp://:8094" data_format = "influx" This configures Telegraf to listen for data on UDP port 8094 in InfluxDB line protocol f

[Next page](<https://devfeed.tech/topics/websocket.md?cursor=WyIyMDI2LTEwLTA5VDA3OjAwOjAwKzAwOjAwIiwgIjNjMWE1YTM3LTJhOTEtNDczNC1hODM4LWNiZDNkODQxYTZmZSJd>)