Conduitry
Conduitry
Presumably because it was easier to set the cookie once and have SK's and the browser's automatic cookie handling take over. I don't know what setting this header on every...
But we'd also need to inject that header into all requests made from the browser as well, right? That's more the part I'm concerned about. I don't think we have...
No, we can't inject the header later. We need to know what version the browser has. That's the whole point of skew protection.
@yannishin Are the appropriate environment variables set at runtime in the built application? https://kit.svelte.dev/docs/adapter-node#environment-variables-origin-protocolheader-hostheader-and-port-header
Ah, okay, if it's in dev mode, then you're not actually running any adapter-node code. What you're asking to do isn't currently supported. We could either add SvelteKit-level configuration for...
See also #9544. This might arguably be a duplicate of that.
Closing as a duplicate of #9544. It's essentially the same gotcha that needs to be documented.
I'm labeling this as a documentation issue. There's not really a way for this to work without trying to evaluate `+page.js` files on the server, which necessarily also tried to...
There have been other issues opened in the past that I can't find right now about the route manifest being public. This is by design. We don't want the browser...
Even if I remove the `bind:value={item.name}` on each ``, I'm seeing the values swap correctly (if I'd previously entered some), which is leading me to believe that the inputs are...