You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problems may be addressed by introducing this feature?
Front end devs are not familiar with the server requirements of reserve proxy and nginx in order to access the REST endpoint.
What benefits does the SDK stand to gain by including this feature?
It will support front end developers better
Are there any disadvantages of including this feature?
It would slightly increase the chance that someone may misconfigure their REST server by accidentally including --insecure that would allow unsecured access.
Proposal
add an --insecure flag to the rest server that adds CORs header with Access-Control-Allow-Origin: *
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
Bring back insecure CORs option for REST server but set the default option off.
#3312
#3317
#4432
#2520
Problem Definition
Front end devs are not familiar with the server requirements of reserve proxy and nginx in order to access the REST endpoint.
It will support front end developers better
It would slightly increase the chance that someone may misconfigure their REST server by accidentally including
--insecure
that would allow unsecured access.Proposal
add an
--insecure
flag to the rest server that adds CORs header withAccess-Control-Allow-Origin: *
For Admin Use
The text was updated successfully, but these errors were encountered: