Safari refusing to use HTTP/2
Bit of a long shot but if anyone has any ideas, please let me know...
I have a tanstack start/db/electric sql setup with an API proxy from the start server -> electric sql, and caddy reverse proxying the start server. Caddy is serving an internal tailscale domain (ts.net) as the route for my dev server, which means it gets HTTPS automatically. On desktop firefox and chrome this setup is enough to get even http/3 connections, while safari on desktop and iOS are refusing to use anything except 1.1, which leads to the now-familiar 6-connection limit issue.
If anyone has any ideas please let me know! I suspect tailscale somehow has smth to do with it but I have no other leads.
3 Replies
xenophobic-harlequin•2mo ago
you might like this pr https://github.com/electric-sql/electric/pull/3221
GitHub
Add
shardSubdomain shape option. by thruflo · Pull Request #3221...Adds an optional shardSubdomain shape option to auto-shard the url subdomain in development:
const url = isProd
? 'https://example.com'
: 'http://localhost:3000&#39...
stormy-gold•2mo ago
This is now released in the latest @electric-sql/client
adverse-sapphireOP•2mo ago
very nice! I can see it doing the sharding but I'm getting 401s on the requests it's making. prolly a misconfiguration on my end but I've been staring at it for a while now, any tips appreciated
it seems like it's bc I 'm already using an API proxy so better auth was rejecting the subdomain requests (first 401, then for cors)
I made it work with some wildcards and adding cors headers