Blog

WebRTC signaling: CORS on REST endpoints, STUN/TURN credentials, and why ICE is not HTTP CORS

ICE connectivity checks use UDP and peer protocols—your REST signaling API still needs CORS for SDP exchange.

1 min read
webrtcstuncors

SFU versus mesh

Selective forwarding units centralize media—CORS matters only on control APIs, not on RTP paths.

Mesh topologies multiply signaling connections—rate limit per origin to prevent abuse.

Debugging

chrome://webrtc-internals shows candidates—correlate with HTTP CORS logs for hybrid failures.

Firewall ALGs can mangle ICE—document required ports separately from CORS.

Back to blog