-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider getting rid of catchall route #800
Comments
If it is only about minimizing execution time it should also be enough to only block the relevant urls like You can export the vercel logs as json and then use the following command to get a list of all URIs: jq ".[].requestPath" logs_result.json -r | sed 's/^[^/]*//' While Vercel offers to export up to 1.000.000 requests, you need to be on a paid plan to really get that many requests, else you only get the amount that you can see for free. Still running that script regulary might give you an overview over problematic urls |
Update: many failed requests are caused by a buggy Fortunately Vercel added observability tab, which nicely sums our invocations in last 12 hours. There is loads of bot attacs like Resolution: we will get rid of the catchall route, in case no route matches just a static 404 will be shown, which also has to include link to the main app + client script to redirect old shortener URLs to new version |
Otherwise all random stuff is routed to
[...all]
and full application is rendered, which takes a lot of execution time.Eg.
/sw.js
/logo/osmapp.png
/wp-admin
TO CONSIDER (!)
We would need to move shortener from
https://osmapp.org/xxxn
to eg.https://osmapp.org/s/xxxn
which would "change permalinks"The text was updated successfully, but these errors were encountered: