luakit / luakit/luakit

[Question] Does luakit support no-cors?

Open
#1,056 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
2.3k
Forks
254
PR merge metrics
No merged PRs in 30d

Description

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 using `no-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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the SPA fetch using `no-cors` in Luakit and compare it with the reported Chrome behavior and the direct `curl` request. Determine whether the request is sent and whether Luakit supports the expected opaque response behavior; done means a confirmed support status with the relevant limitation documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, lua
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.