Hey Eric,

in this approach as soon as there is an error, you will always seen an error (even if future requests return 200). That’s because you never “reset” the history state for the particular url on 200 code responses, you just keep it to whatever it already was. The downside is that some 404 responses shouldn’t trigger a 404 page, but that’s solvable with some custom logic