直播更改日志

- hostPort may be blocked by firewall rules - NodePort 30843 is in valid range (30000-32767) - Browser connects to external port 8443 - Router forwards 8443 -> ...

- ConfigMap was missing SSL config from application.yml - Added server.ssl settings with environment variable support - Matches local application.yml configurat...

- NodePort range is 30000-32767, cannot use 8443 - Use hostPort to bind directly to host port 8443 - Removed service-websocket.yaml

-浏览器WebSocket API不支持HTTP/2(RFC 8441未执行) - 原生WebSocket需要HTTP/1.1 升级失败于 HTTP/2 - 让SockJS自动选择运输(xhr -- -- 流/xhr -- -- 通过HTTP/2) - 修复与 HTTP/2 的 WebSocket 连接失败

- Changed /ws route from HostRegexp to Host(media.kamocrm.com) - TLSOption can only be applied to explicit hosts (not regex) - ALPN negotiation happens during T...

- Created media-tls-http1 TLSOption with alpnProtocols: [http/1.1] - Referenced ONLY in media-route IngressRoute - Does not affect other Traefik routes - Fixes ...

- Added two routes: /ws for WebSocket (higher priority), rest for API - Only /ws uses media-websocket-transport (HTTP/2 disabled) - API routes can use HTTP/2 fo...

- Simplified to Host(media.kamocrm.com) - Avoids regex escaping issues with backticks - Tests show route is working with simple Host match

- Created TLSOption to disable HTTP/2 ALPN negotiation - Forces browsers to use HTTP/1.1 for media.kamocrm.com - WebSocket upgrades require HTTP/1.1 protocol - ...

- Added idleTimeout=0 to websecure entrypoint - Prevents Traefik from closing WebSocket connections due to inactivity - Fixes SockJS WebSocket timeout issues

- 将SockJS运输从[websocket,xhr-streaming,xhr-poling]改为[websocket] - 取消回落投票 - 纯网络锁接力 - 如果WebSocket不起作用,而不是有辱人格,那么失败的速度会很快

- 两种服务同名空间(kamo) - 不需要明确的名称空间参考 - 避免潜在的跨名称空间问题

- 已删除 Next.js 为/ws 路径重写 - 现由Traefik IngressRoute处理的WebSocket线路 - Traefik 内部路线.kamocrm.com/ws - > 直接媒体服务

- 为入侵鲁特的路径增加专用路线 - 内部路线.kamocrm.com/ws - > 直接媒体服务 - 在WebSocket支助中使用与媒体路线相同的服务器运输 - 用于 WebSocket 连接的 Bypasses Next.js(Next.js 重写不支持 WS) - 更具体的路线首先与一般路线相匹配

- 将路径添加到中间软件绕行 - SockJS 需要连接到/ws/info而不重定向 - WebSocket连接仍然有 *** cookie - 解决WebSocket连接超时问题

- 从media.kamocrm.com改为同源(内部.kamocrm.com) - 避免出现交叉来源的WebSocket连接问题 - 添加 Next.js 重写规则到代理/ws 到 Media Service - 浏览器将连接到内部.kamocrm.com/ws - Next.js将代理到媒体.kamocrm.com...

- Traefik error: cross-namespace format not allowed when crossnamespace disabled - IngressRoute and ServersTransport are in same namespace (kamo) - Use simple n...

- 使用简单的视频:屏幕共享真实性 - 建设现在应该成功

- 手机图标在@mui/icons-materi中不存在 - 使用CallEnd,这是正确的MUI图标 - 删除未使用的重复文件(ChatBox With WebRTC、VideoCallView、使用JanusWebRTC) - 建设现在应该成功

- Coturn relay: 52000-65535 (13,536 ports) - Avoids: Janus RTP (10000-49151) and WireGuard (51820-51821) - No overlap between services

- Changed max-port from 65535 to 51800 to avoid conflicts - Avoids WireGuard on UDP 51820 and other VPN services on 51821 - Provides 2,649 ports (49152-51800) f...

- Replace netstat-based health probes with TCP socket checks (netstat not available in coturn/coturn:latest Alpine image) - Remove conflicting no-stdout-log dir...

Traefik requires the @kubernetescrd suffix when referencing CRD resources like ServersTransport.

Remove media-websocket-upgrade middleware that was forcing headers and causing WebSocket handshake issues. Traefik automatically handles WebSocket upgrade when ...

- 使用xhr-流线和xhr-波程运输,而不是网络锁 - 这些运输与HTTP/1.1和HTTP/2同时工作,不需要WebSocket升级 - 避免HTTP/2扩展的CONNECT问题并改进标题转发问题 - /ws/info 请求在 HTTP/2 中及时出局(499起),使 SockJS 无法连接

- Add $ to end of PathRegexp to ensure exact match - Fixes regex parsing error in Traefik - /ws/info is now working (200 OK) but WebSocket upgrade route needs p...

- Change route match from PathPrefix(/ws/) to **************** - /ws/info is a regular HTTP request, not a WebSocket upgrade - Adding Upgrade header to /ws/info...

- Add Connection: Upgrade header along with Upgrade: websocket - Both headers are required for proper WebSocket upgrade handshake - This ensures HTTP/2 Extended...

- Create separate route matching /ws/** paths with media-websocket-upgrade middleware - This ensures Upgrade: websocket header is added for WebSocket upgrade re...

- Create ServersTransport resource with disableHTTP2: true - Reference ServersTransport in IngressRoute service configuration - Remove invalid disableHTTP2 fiel...

- 添加禁用HTTP2: 将 HTTP/1.1 强制用于后端连接 - HTTP/2 扩展 CONNECT 没有正确转换升级头 - WebSocket升级需要HTTP/1.1升级:websocket头 - 此修正 WebSocket 握手时的“ 升级头: 无效” 错误

- Set scheme: http to ensure proper HTTP/1.1 handling for WebSocket upgrades - HTTP/2 Extended CONNECT needs proper conversion to HTTP/1.1 Upgrade header - This...

- Remove invalid DefaultHandshakeHandler override (method doesn't exist) - Remove invalid setSupressCors call (method doesn't exist) - Keep HttpSessionHandshake...

- Add handshake handler and interceptor logging to diagnose WebSocket connection issues - Configure SockJS to suppress CORS (handled by Spring Security) and dis...

- 明确配置SockJS运输订单,以选择WebSocket,然后回落到xhr-流/xhr-波 - HTTP/2 WebSocket升级可能失败,SockJS将自动回落到HTTP/1.1相容的运输上 - 这将解决浏览器使用 HTTP/2 时的 WebSocket 连接超时

- media-cors middleware was clearing CORS headers which interfered with WebSocket upgrades - WebSocket connections require direct pass-through without header mo...

- PatternParseException: No more pattern data allowed after {*...} or ** - /ws/** already covers all paths under /ws including /ws/info - This was causing 500 e...

- Apply media-cors middleware to allow CORS headers for WebSocket connections - Matches the pattern used for theme domains

- Add explicit permit for OPTIONS method on all paths - Add explicit permit for /ws/info endpoint (SockJS handshake) - This ensures CORS preflight requests reac...

- Explicitly handle '*' wildcard for origins, methods, and headers - Add WebSocket-related headers to exposed headers - Add logging to verify CORS configuration...

- Add logging to verify WebSocket endpoint registration - Configure SockJS heartbeat and disconnect delay - This should help diagnose why SockJS handshake isn't...

- 新增记录以核实路线被击中 - 路线文件存在,Next.js 15的结构是正确的

- STOMP (英语) 客户端没有“ 活动” 属性 - 只检查“ 连接” 属性, 该属性为正确的状态指标

- 在WebSocketError上不是客户端选项中的有效属性 - SockJS 错误处理器( 错误, 关闭) 已经提供了错误处理

- 添加SockJS出错处理器(打开、打开、关闭)以捕获连接故障 - 添加连接超时检测(10秒)以识别无声故障 - 在WebSocketError处理器上添加到STOMP客户端 - 改进记录,以确定WebSocket连接为何没有建立 - 这将有助于识别 SockJS /ws/info 请求是否失败

- Removed duplicate /ws endpoint registration (SockJS already handles native WebSocket) - Added null check for payload in subscribeToSession - This may fix WebS...

- Spring Security does not allow path segments after /** pattern - /ws/** already matches all paths under /ws including websocket endpoints - This fixes Pattern...

- 绕过证书验证的还原更改 - 证书由自动证书服务(让我们加密)签发,而不是自签名 - 需要调查验证失败的原因