CORS Issue with Fastify and Socket.IO Configuration about fastify-cors HOT 6 CLOSED

Thanks for reporting!

Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that.

from fastify-cors.

Please provide the screenshot in broswer or cURL about the headers for both request and response.
You can mask the sensitive information. I would like to double confirm is the header properly sent.

For example, is the browser providing the Origin header.

If you are using reverse proxy in between, please also check if the headers are hide by that proxy.
It is often that the proxy is not properly proxy CORS headers and requires some manual config.

from fastify-cors.

This is what I'm getting in my browser

from fastify-cors.

This screenshot is not going to helps.
You should provide that contain the headers for both request and response.

from fastify-cors.

I am closing the issue because I believe it is the problem related to socket.io.
socket.io used to be overriding the request handling of fastify, so you should configure the CORS from socket.io side.

from fastify-cors.

Yes, you are correct... the issue is in socket.io side, Thank you

from fastify-cors.