Timeline for How to effectively handle 404/500 http errors in server-side rendering web application which uses store for state?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 14, 2019 at 21:00 | history | bounty ended | CommunityBot | ||
| S Sep 14, 2019 at 21:00 | history | notice removed | CommunityBot | ||
| Sep 12, 2019 at 8:12 | answer | added | MTJ | timeline score: 0 | |
| Sep 11, 2019 at 14:32 | answer | added | Dan Monego | timeline score: 1 | |
| Sep 9, 2019 at 13:38 | comment | added | Laiv | The race conditions might be telling you that you need to synchronize these executions. Or break the execution and redirect immediately when errors happen. Or wait until all the processes have finished for solving the final state of "internalError". | |
| Sep 7, 2019 at 20:59 | comment | added | Thomas Junk | I think the scope of this question is too broad. Partly because unless you give more details, there are a bunch of ways to solve this problem: e.g. routing to available countries could at least be solved at the initial loading of the page. There are perhaps many more cogwheels for this to adjust. The general answer would be with good design but this answer would be of no help. | |
| S Sep 6, 2019 at 19:26 | history | bounty started | Yos | ||
| S Sep 6, 2019 at 19:26 | history | notice added | Yos | Authoritative reference needed | |
| Sep 4, 2019 at 18:36 | history | asked | Yos | CC BY-SA 4.0 |