tRPCttRPC
Powered by
DiamondDragonD
tRPC•3y ago•
4 replies
DiamondDragon

CORS issue with Lambda Handler (SST)

no idea what's going on with this error. been stuck on it for way too long. i tried adding the test-header to the server side but not seeing it come through? should that happen?

i went through this issue but doesn't seem to work for me

Access to fetch at 'https://x.execute-api.us-west-2.amazonaws.com/properties.fetchProperties?batch=1' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Access to fetch at 'https://x.execute-api.us-west-2.amazonaws.com/properties.fetchProperties?batch=1' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
image.png
image.png
image.png
tRPCJoin
Move Fast & Break Nothing. End-to-end typesafe APIs made easy.
5,015Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

TRCP JSON Malformed When Deployed to Lambda Using SST
Answer OverflowAAnswer Overflow / ❓-help
2y ago
SSE issue with CORS and Fastify
mh15Mmh15 / ❓-help
10mo ago