Now, CORS also requests the "Access-Control-Allow-Credentials" to be set to true.
Can we have the --unrestricted-api to add that flag as well? The full list is:
"Access-Control-Allow-Origin": [
"http://localhost:5001",
"http://localhost:8888"
],
"Access-Control-Allow-Methods": [
"PUT",
"GET",
"POST"
],
"Access-Control-Allow-Credentials": [
"true"
]
//cc @whyrusleeping
I think that makes sense to do. That flag should really mean "let me do whatever i want with the API now"
It probably should say --insecure-api to be super clear.
ipfs daemon --president-madagascar=false
On Tue, Aug 9, 2016 at 12:09 Jeromy Johnson [email protected]
wrote:
I think that makes sense to do. That flag should really mean "let me do
whatever i want with the API now"—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/go-ipfs/issues/3058#issuecomment-238603494, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIcoYZA-t4aZq3LvmeFC-0FhwKOSdCUks5qeKY2gaJpZM4Je981
.
ipfs daemon --world-domination=true --do-that-one-thing-with-the-giraffe=false --redisenable-discombobulated-inhibitors
Yeah, lets make things do what they say
ipfs --i-know-what-im-doing because if you have to ask what it does, you probably shouldn't be using it.
I'd like to avoid adding new flags to the daemon, but if this can be set through config, we may just add a config profile for this.