Now, here’s the thing that surprises most folks. Even if your API is hosted on a subdomain, e.g. api.example.com, the browser still sees it as a cross-origin request from example.com. Moving the API to example.com/api will eliminate the need for preflight requests altogether. - ThreadSky

About ThreadSky

theburningmonk.com • 52 days ago

Now, here’s the thing that surprises most folks.

Even if your API is hosted on a subdomain, e.g. https://api.example.com, the browser still sees it as a cross-origin request from https://example.com.

Moving the API to https://example.com/api will eliminate the need for preflight requests altogether.

Comments

theburningmonk.com•52 days ago

Of course, subdomains aren’t inherently bad, and many organizations prefer them to organize multiple APIs and environments. And maybe even let teams have their own subdomains and allow them to be more autonomous.

theburningmonk.com•52 days ago

But for personal projects or side hustles, where margins are tight, cutting these unnecessary costs can make a meaningful difference.

theburningmonk.com•52 days ago

You can also put CloudFront in front of your API and cache and handle these preflight requests at a lower cost. This doesn’t eliminate preflight request-related charges entirely, but it goes a long way to minimize it.

theburningmonk.com•52 days ago

If you liked this, then you might also enjoy the tips and tutorials I publish every week about AWS and serverless.

Subscribe to my free newsletter and level up your AWS game: https://theburningmonk.com/subscribe

pawelpiwosz.bsky.social•52 days ago

I don't know how, but in some crazy way I missed your newsletter. It is fixed already ;)

theburningmonk.com•51 days ago

Thank you 🙏

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply