Pitfalls

Whenever there's a possible pitfall discovered, it will be added to this page.

Route / asset collision

DASPRiD pointed out that it's possible to get weird behavior when you have colliding routes. Example, if you're serving an asset named myasset.png and you also have a route that goes to myasset.png they will have a different behavior with cache enabled, as opposed to cache disabled. The fix to this seems obvious to me, simply don't create colliding routes. This should not happen to you, but if it does, you now know why.