cli: Add a wait screen (HTML) instead of a plain text error when reverse proxy hits a non-started server #5044
Conversation
- render waiting HTML with proxied error details instead of raw 500 text - auto-reload once backend responds to unblock fullstack UI - add html-escape for safe error embedding
|
Instead of making this error screen nicer, could we just avoid it entirely by waiting until the proxy responds before sending the reload message to |
|
So... that'd work, but it would presumably not work on startup – only on reload, right? As in... if you started The only way I could see 'waiting' work is if the proxy just held the connection open and stalled (not responding) until the upstream responded? Am I... understanding that right? |
Currently while building you get a loading screen that shows the progress of the build that redirects to the finished page once it is ready. Ideally we could re-use that same screen here by just not sending the reload request until the server boots. The loading screen uses an incomplete http response to keep the socket open so it doesn't register as loaded in the browser for playwright tests |
3 participants
When waiting for the backend to load in fullstack builds, we currently see an error message that's a plaintext response from the reverse proxy, which... stalls out reload workflows, hard. If doing a full rebuild, you can end up hitting this screen, and then you have to go refresh all the windows that got stuck here.
This PR adds a simple HTML page that shows the error templated in, but tries to refresh periodically, trying to get to a working version of the page.
To save from it looking ugly as sin, I had an LLM generate inline styling here and it's... very aesthetic, but happy to adjust to match Dioxus's styling as appropriate!