#Good ideas for disabling API endpoints in production?

4 messages · Page 1 of 1 (latest)

severe junco
#

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?

mortal pilotBOT
#

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

      🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in <id:customize>

      ✅ You can mark a message as the answer for your post with `Right click -> Apps -> Mark Solution`
      (if you don't see the option, try refreshing Discord with Ctrl + R)
agile horizon
#

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.

hasty hinge
#

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