Problems with Blurt RPC nodes

This post is for RPC node runners like @megadrive @khrom @dagobert @drakernoise @saboin @tekraze -Please spread the word to all node runners!! We're getting very very close to releasing Morphit a true DEX/BBS for Blurt , but need at least a few RPC nodes to connect to. We have a list of 6 different RPC nodes, but 3 of them are giving us problems. Can you guys please update your RPC nodes so that we can utilize them too? The RPC nodes with problems are: - rpc.beblurt.com, blurtrpc.dagobert.uk and rpc.blurt.one When a website running in someone's browser tries to pull data from a different domain, the browser does a safety check before handing the data over. It only lets the website read the response if the server includes a little permission slip — an HTTP response header called Access-Control-Allow-Origin — that says "yes, websites from other domains may read me." No slip, or a malforme…

JSON-RPC POSTs Content-Type: application/json trigger a CORS preflight; answer it cheaply so the real POST is allowed through: if $request method = OPTIONS add header 'Access-Control-Allow-Origin' ' ' always; add header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always; add header 'Access-Control-Allow-Headers' 'Content-Type' always; add header 'Content-Length' 0; return 204; proxy hide header 'Access-Control-Allow-Origin'; add header 'Access-Control-Allow-Origin' ' ' always; curl -H 'Origin: -sI grep -i access-control-allow-origin A good result is exactly one line — Access-Control-Allow-Origin: . Zero lines means it's still missing; two lines means it's still doubled. PLEASE PLEASE PLEASE pass this message along to those node owners. I do not have access to discord, telegram, etc. Let's make proper availability/use of those nodes 🙏

@megadrive @khrom @dagobert @drakernoise @saboin @tekraze