Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OPTIONS HTTP request may not ask for autorization headers #83

Open
TheoLechemia opened this issue Jan 27, 2023 · 0 comments
Open

OPTIONS HTTP request may not ask for autorization headers #83

TheoLechemia opened this issue Jan 27, 2023 · 0 comments

Comments

@TheoLechemia
Copy link
Contributor

Hello,

As I mentionned in the IstSOS google group we have developped a small frontend to see sensors and plot their data based on the istSOS API : https://groups.google.com/g/istsos/c/YIl6tFgs7So
Everything work well until we put serve our application behind a domain (different that the istSOS one) ang got CORS issues.
Our istSOS is protected by the HTTP Basic Authentication following the dedicated doc, but the istSOS always check the authentification, even for OPTIONS request (which it looks like to be not standard : https://fetch.spec.whatwg.org/#http-responses)
I had to "hack" a little bit my Apache conf to manage this issue :

SetEnvIf Request_Method "OPTIONS" noauth=1
        <RequireAny>
            Require env noauth
            Require valid-user
        </RequireAny>

but maybe it would better to do it at the application level.
I could propose a pull request if you aggree with this evolution ?

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant