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

Self signed certificates don't lead to error but just to blank page #1615

Open
Utopiah opened this issue Nov 3, 2024 · 0 comments
Open

Self signed certificates don't lead to error but just to blank page #1615

Utopiah opened this issue Nov 3, 2024 · 0 comments
Labels
bug Something isn't working chromium Issues related to the new Chromium backend

Comments

@Utopiah
Copy link

Utopiah commented Nov 3, 2024

Configuration

Wolvic version: Wolvic Chromium 1.1
Wolvic build ID: 183021044

Hardware: Quest 3

Steps to Reproduce

  1. Open a self-signed HTTPS website or a website with an expired certificate

Current Behavior

Get a blank page, no content, no error or warning

Expected Behavior

Expect a warning or error message, ideally allowing to accept and go through anyway

Possible Solution

Follow what the Quest or Chrome or Firefox do, namely provide the option to accept temporarily the certificate after showing the problem

Context

Developing content often means self-hosting on LAN urls, e.g. https://192.168.0.123:3000/index.html and providing HTTPS is required to get WebXR.

Error Logs and Stack Traces

@svillar svillar added bug Something isn't working chromium Issues related to the new Chromium backend labels Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chromium Issues related to the new Chromium backend
Projects
None yet
Development

No branches or pull requests

2 participants