π΅
Hello, CORSness, my old friend
I've come to talk with you again
As I've experienced repeatedly for years, #CORS (#CrossOriginResourceSharing) is notoriously difficult to understand, reason about and implement. So I should not be surprised to find a problem in #Quarkus related to it, and that it has gone unnoticed for years. #Sigh
I hope the bug report I wrote is clear and actionable: https://github.com/quarkusio/quarkus/issues/51541
I'd like to migrate @ChronoLink to Quarkus, but this bug is a showstopper for that: the obvious workaround - opening up POST/PUT/DELETE to CORS - feels risky.
Speaking of risk: this being a hobby project means there is a real risk I won't find the time or energy to write the reproducer the Quarkus team rightly asks for. Oh well...
CORS filter complains about "wrong" method on same-origin POST request Β· Issue #51541 Β· quarkusio/quarkus
Describe the bug I run a Quarkus application on https://settings.example.com and an associated static web site on https://www.example.com. Here's the CORS config: quarkus.http.cors.enabled=true qua...