Reply to this note

Please Login to reply.

Discussion

I think browser’s don’t follow redirects by default, your client would have to explicitly allow that.

#[4] HTTP 301s respected?

Resolved! It was CORS

My CORS headers never changed. My bet is caching.

It’s always caching.

Unless it’s DNS.

Access to fetch at 'https://shawnyeager.com/.well-known/lnurlp/shawn' from origin '...' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Thanks. I’m using Netlify, so this is in a .toml file, but I should be good.

[[headers]]

for = "/.well-known/*"

[headers.values]

Access-Control-Allow-Origin = "*"

i your [[redirects]] after to = "", you can add a new line with:

headers = { } to add the ACAO

quote: This returns the 301 response but with the “x-from: Netlify” header. If there are other questions, please let us know.