Quiz · 4 questions
🏠 Talking to the Engine at Home
Thin clients, hardened URLSession, the lone ATS key, a Swift engine behind Serve twins, WebSockets that reconnect honestly, and an outbox that never loses a capture
Level 0Bundle Opener
0 XP0/81 lessons0/17 achievements
0/100 XP to next level100 XP to go0% complete
Quiz
01A client's Info.plist has both NSAllowsArbitraryLoads and NSAllowsLocalNetworking set to true. Plain-HTTP requests to the engine's tailnet twin fail with -1022, while curl from the same Mac gets 200. What fixes it?
02A Swift engine listens with NWListener on 127.0.0.1:7200. After Tailscale Serve starts publishing an HTTP twin on port 7200, every launchd respawn fails with EADDRINUSE. What is going on?
03An outbox drain sends its first entry and the engine answers 401 because the session expired. What should the drain do?
04A phone client's URLSessionWebSocketTask reports state .running, but the Mac at home went to sleep ten minutes ago. How does the client find out?
Comments 0
🔔 Reply notifications (sign in)Sign in — Please sign in to comment.
No comments yet — be the first.