Preskoči na glavni sadržaj
🔒 Način pregleda. Prvih petnaest Foundations lekcija je besplatno; ova je Pro. Pokrenite 7-dnevni trial da otključate editor, AI savjete i ostatak programa. Kartica obavezna, otkažite bilo kada u Dashboard.
Pokreni 7-dnevni trial →
⚡
← Kolegiji
›
FastAPI Production
›
Modul 5 · Razvoj proizvodnje i mogućnost promatranja
›
SSE i strujanje odgovora
quiz
69 / 105
🇭🇷
HR
▼
↗
Podijeli
⋯
Više
+100 XP
📋
Zadatak
📖
Teorija
🤖
AI Pomoć
Zadatak
🌐 shown in EN
📝 **Question:** Why send keepalive lines on an SSE stream? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Kviz
Pitanje
📝 **Question:** Why send keepalive lines on an SSE stream? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Browsers require a comment line at least every 30 seconds or they will close the EventSource connection with a network error, so the comment is purely a client-side compatibility requirement
B
Proxies (nginx, ALB, Cloudflare) close idle HTTP connections after 30-60s of silence
C
The SSE specification mandates a colon-prefixed line as the wire-level heartbeat — without it, conforming clients refuse to dispatch any events at all to the application layer above the parser
D
It exists only to make traffic visible during debugging — without periodic comments you can't tell whether the stream is healthy or just quiet, but production code can safely omit it entirely
Odgovori
💬
Kontaktiraj podršku