Needs Investigationenhancementhelp wanted
Métriques du dépôt
- Stars
- (9 831 stars)
- Métriques de merge PR
- (Merge moyen 9j 12h) (116 PRs mergées en 30 j)
Description
Is there any way to tell Visdom to make requests over HTTPS as opposed to HTTP?
When setting up a reverse proxy with HTTPS, pointing to localhost:8097, I get these messages (Chrome).
Mixed Content: The page at 'https://my.web.address/' was loaded over HTTPS, but requested an insecure script 'http://my.web.address/static/js/main.js?v=4b72317f763632006def9236be6408b4'. This content should also be served over HTTPS.
Which is fine for development purposes, however I also receive this error message that I'm not sure how to resolve.
WebSocket connection to 'ws://my.web.address/socket' failed: Error during WebSocket handshake: Unexpected response code: 301
And this (Edge)
SCRIPT5022: SecurityError
main.js (1,13767)
For completeness, here's the Caddy configuration on how I'm reverse proxying Visdom.
my.web.address {
proxy / localhost:8097 {
transparent
websocket
}
log stdout
errors stderr
}