From 01a3090c6ab872621e01019c58f8cac38c354c25 Mon Sep 17 00:00:00 2001 From: Luke Childs Date: Fri, 6 Jan 2023 19:37:55 +0700 Subject: [PATCH] NIP05 Improve CORS header check command --- 05.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/05.md b/05.md index 437c637f..a67f530e 100644 --- a/05.md +++ b/05.md @@ -83,7 +83,7 @@ By adding the `` as a query string instead of as part of the path th JavaScript Nostr apps may be restricted by browser [CORS][] policies that prevent them from accessing `/.well-known/nostr.json` on the user's domain. When CORS prevents JS from loading a resource, the JS program sees it as a network failure identical to the resource not existing, so it is not possible for a pure-JS app to tell the user for certain that the failure was caused by a CORS issue. JS Nostr apps that see network failures requesting `/.well-known/nostr.json` files may want to recommend to users that they check the CORS policy of their servers, e.g.: ```bash -$ curl -sI https://example.com/.well-known/nostr.json?name=bob | grep ^Access-Control +$ curl -sI https://example.com/.well-known/nostr.json?name=bob | grep -i ^Access-Control Access-Control-Allow-Origin: * ```