fix(web): WebSocket scheme follows page protocol (wss:// under TLS) #150
No reviewers
Labels
No labels
blocked
bug
compat
docs
documentation
duplicate
emry-cli
emry-core
emry-engine
emry-ingest
emry-py
emry-store
emry-tui
emry-web
enhancement
good first issue
gpu-compute
help wanted
hpc
infra
integrations
invalid
needs-design
P0-blocker
P1-core
P2-enhanced
P3-future
performance
pull-request
python
pytorch
question
rust
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
femboy/emry!150
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/web-ws-tls-scheme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The dashboard hardcoded
ws://, soemry web --tls-certserved over HTTPS had its live stream blocked as mixed content (chart never updated). Now deriveswss:///ws://fromlocation.protocol. Plaintext behaviour unchanged; index_serves_html test updated. Follow-up flagged during the #149 review.The dashboard hardcoded `ws://${location.host}/ws`, so when `emry web` is served over HTTPS (`--tls-cert`/`--tls-key`) the browser blocks the live stream as mixed content and the chart never updates. Derive the scheme from `location.protocol`: `wss://` on an https page, `ws://` otherwise. Plaintext (http) behaviour is unchanged. Updated the index_serves_html test to assert the scheme-following wiring instead of a literal ws://.