[Suggestion]: Add section in readme about exposing headers #33
Description
What happened?
Hello,
Sorry for making a suggestion as a bug report. I could not find any suggestions/discussion options.
I realize we should be at the top of our CORS/CSP game in 2025, but in my opinion it would be helpful to add a section in the README.md that reminds the user to expose the TUS-related headers in case of CORS, using Access-Control-Expose-Headers, and possibly even provide a static array they can call in their cors.php config file.
Without exposing the headers, the front-end TUS client will fail because the browser only makes a limited number of headers available to JavaScript in case of cross-origin requests. More here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers
Just wasted an hour trying to figure out why the "Location" header was missing on my frontend (completely my fault, and no blame on your package).
How to reproduce the bug
Not a bug, I'm sorry.
Package Version
PHP Version
Laravel Version
Which operating systems does with happen with?
No response
Notes
No response