-
Notifications
You must be signed in to change notification settings - Fork 251
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
[Question] Does luakit support no-cors? #1056
Comments
Well, again, i don't really understand the technologies you're playing with, so the below may be unhelpful/incorrect.
|
The idea behind CORS is that in order to make a HTTP call from JavaScript (nowadays with the So this is a security feature provided by the browser (and all the browsers I know implement it) so if a site you want to There is one more workaround, which is to say to the browser "please make the call anyway but do not tell me anything about its result". This is called an opaque call and is driven by the
I will give this a try tonight. So far I used Luakit only as a "programmatically driven browser" - it is in kiosk mode and there are no interactions with it (no keyboard nor mouse). I will plug these in tonight and see how it works (and learn about |
Hi, I'm trying to setup a headless "kiosk" (more like a Linux-powered dashboard screen of sort) and the only browser with decent performance on my Raspberry Pi 1 B is luakit. I'd like to know if there's a solution to this, because my website (a GUI addon on top of Google Calendar's ICAL) needs CORS bypass. Thanks |
I have a case where I need to make a
fetch
from within an SPA to an endpoint that does not provide CORS headers. I am fine with making an opaque call usingno-cors
.When testing my code on my laptop with Chrome, I get the expected behavior (a successful call to the backend without any response because of the nature of
no-cors
)When moving the code to a server with Luakit the calls are not sent from the SPA (everything else works).
When making a direct
curl
call from that server it reaches the backend as expected.It is not easy for me to debug on that server so before engaging in heavy-duty cables and connections reorganization I wanted to make sure that
no-cors
is supported by Luakit in the first place.If this is the case (I am pretty sure that it is) I will go further with my tests.
The text was updated successfully, but these errors were encountered: