CORS? It's always CORS!
#[0] any usual suspects that would cause my (custom domain) NIP-05 to get flagged as false in iris.to, even though it shows up on my damus profile? https://agbeg.in/.well-known/nostr.json
Discussion
I was wondering about that. Lol dammit. Is that something I change in domain/dns? A file upload? Anybody posted how-to fix the CORS issue recently?
depending on your web server or host config.
.htaccess file
Header set Access-Control-Allow-Origin "*"
it looks like you're using netlify?
https://stackoverflow.com/questions/62507022/how-to-enable-cors-on-a-netlify-deployment
I’ma zap the hell outta you if this works
also, redirects (308, etc) are not permitted as per security standards of nip05. this is a simple dumb thing that tripped me up. clients are instructed not to follow redirects. that will yield a red herring CORS issue
also, if this well known json will rarely change, set cache control for aggressive dns/client caching. will save you 100-1000x bandwidth
Muchas gracias amigo!
?raw=true
it depends on your webserver. by the way iris is showing your nip-05 ok.
Just fixed thanks to article shared by #[2] ! 🤙
you can add your preferred relays on your nostr.json on your webserver. just check the https://nips.be/5 implementation aka NIP-05. You can add a separate tag on that json file to refer the relays you prefer! Cheers!
Noicee 🙌🤙
