Replies: 1 comment
-
After some research, I found out that:
So, to fix it you probably need to add it somewhere on your server side around the CORS configuration:
Hope this helps |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am working on retrieving a specific server-sent header using a custom link with tRPC. This methodology works flawlessly during testing, but issues arise when I implement it in the client browser (the latest Chrome).
In the browser, the list of headers only contains Content-Type and Content-Length. However, I can confirm that the header I am seeking is present as it's visible within Chrome's developer tools.
Could you help me understand why the header is not appearing as expected when using the custom link in the client browser, even though it's clearly present and visible in the developer tools?
Here is my implementation of the custom link builder:
Beta Was this translation helpful? Give feedback.
All reactions