Support different status code pages, 301, 302, 404 ( I saw that not found pages would work properly in the near future, but would be good if we can set the status code for those pages properly as well)
If a user wants to have pages on the frontend for handling common HTTP statuses, like 404 most commonly, but also 500, 302, 301, ... -> what can they do right now?
They can do "catch all" route for 404, but for the rest they are left to their own. Well even the 404 solution is quite manual.
It is not yet clear to me what is the best solution here nor what do ideally users want / need, we should investigate this first and then figure out what we want to do about it. We should check what other frameworks do + what our users say.
We haven't had a ton of requests for this, but we did have a couple, so there is some need it seems.
Martinsos
commented
1 month ago
User said on Discord:
If a user wants to have pages on the frontend for handling common HTTP statuses, like 404 most commonly, but also 500, 302, 301, ... -> what can they do right now?
They can do "catch all" route for 404, but for the rest they are left to their own. Well even the 404 solution is quite manual.
It is not yet clear to me what is the best solution here nor what do ideally users want / need, we should investigate this first and then figure out what we want to do about it. We should check what other frameworks do + what our users say.
We haven't had a ton of requests for this, but we did have a couple, so there is some need it seems.