Good ideas for disabling API endpoints in production?
Unanswered
New Guinea Freshwater Crocodile posted this in #help-forum
![Avatar](https://cdn.discordapp.com/embed/avatars/3.png)
New Guinea Freshwater CrocodileOP
Is there a way to disable certain routes in production?
I know I could just put an env check and just return 404, but is there some way disabling the rules based on the env.
Is middleware the right answer?
I know I could just put an env check and just return 404, but is there some way disabling the rules based on the env.
Is middleware the right answer?
3 Replies
![Avatar](https://cdn.discordapp.com/avatars/809942393637306400/1e4e5a29a08b96de9a1e3d3520b5e771.webp?size=256)
tafutada777
middlewar.ts, which is deployed to Edge, works as if it were a reverse proxy so as the official documentation says you can implement personalization, i18n, authorization, rate limit, tailor headers and so on. plus traffic won’t hit AWS Lambda.
![Avatar](https://cdn.discordapp.com/avatars/484037068239142956/44415017de6fed2ccd5d44b4b2051ac0.webp?size=256)
joulev
you can also use redirect in next.config.js to redirect traffic to those paths; it won't require making a middleware file but won't be as flexible as middleware
![Avatar](https://cdn.discordapp.com/embed/avatars/3.png)
New Guinea Freshwater CrocodileOP
thanks guys