nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

The next. version of noStrudel forces wss:// for all my Tor relays. SSL would not be necessary here. It would be great if onion addresses were excluded from the enforcement of wss:// and ws:// remained possible.

Reply to this note

Please Login to reply.

Discussion

This isn't something I have control over, the hosting provider I'm using for the next version is automatically applying the `upgrade-insecure-requests` CSP rule https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests

Working on a better hosting solution, but until then the next version can connect to ws:// or http:// 😞

Did you just change that, as it wasn't working the day before yesterday.

Bei der normalen Version geht es. Nur auf next.nostrudel.ninja habe ich das Problem.

Bei mir auch. Auf Next geht es nicht.