Chat: cannot wait for changes in a file if file for today hasn't been created yet

The long chat system only creates a file for chat in a given day if someone actually sends a message. After it is created, each user of the chat subscribes to web socket events when the file changes.
Anyone opening the chat before the file for today has been created gets an error because it hasn't got a 200 response from the file and so can't look at the headers in that.

But in fact the 404 response does have a Updates-Via: wss://example.com header.

So it needs the rdflib function which looks at the headers at it to also look at 404 responses.
And it needs the server to allow one to watch for a non existent file being created.

Start by locating the long chat file handling and the rdflib function that reads the Updates-Via header. Trace how 404 responses and websocket subscriptions are handled, then verify the server path for watching a file that does not yet exist. Done means a chat opened before today’s file exists can wait for its creation without an error.