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

WASM examples could not fetch whisper models due to CORS #2210

Open
Heaper327 opened this issue Jun 4, 2024 · 0 comments
Open

WASM examples could not fetch whisper models due to CORS #2210

Heaper327 opened this issue Jun 4, 2024 · 0 comments

Comments

@Heaper327
Copy link

Attempts to run whisper.wasm, stream.wasm, and bench.wasm examples from a locally hosted server all failed, as the website could not fetch whisper models from whisper.ggerganov.com due to CORS:
Screenshot 2024-06-04 at 10 10 13 PM
Closer inspection shows that whisper.ggerganov.com responds with the following header, with no Access-Control-Allow-Origin entry:

HTTP/1.1 200 OK
Server: nginx/1.18.0 (Ubuntu)
Date: Tue, 04 Jun 2024 14:03:27 GMT
Content-Type: application/octet-stream
Content-Length: 32166155
Last-Modified: Sun, 14 May 2023 15:38:57 GMT
Connection: keep-alive
ETag: "64610091-1ead10b"
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Accept-Ranges: bytes

Would it be possible for whisper.ggerganov.com to add Access-Control-Allow-Origin: * to its response header? Or do we just have to change the fetch url to a localhost url for development purposes?

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