Update CORS policy

[piotr-yuxuan]

$ curl -X GET -i http://localhost:8081/config
HTTP/1.1 200 OK
Date: Fri, 12 Jul 2019 23:07:20 GMT
Content-Type: application/vnd.schemaregistry.v1+json
Vary: Accept-Encoding, User-Agent
Content-Length: 29
Server: Jetty(9.4.14.v20181114)

{"compatibilityLevel":"FULL"}%

Using standard, up-to-date schema-registry shipped in Confluent CLI, response doesn't deal with CORS. As such it breaks this useful side project lensesio/schema-registry-ui#88:

Access to XMLHttpRequest at 'http://localhost:8081/config' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Would you mind state whether you might fix this? If yes, could you provide a link to check progress made on that issue and when it's solved?

Cheerio ;-)

[piotr-yuxuan]

In my humble opinion, at least same domain should be allowed. It would be nice to have a list of custom allowed origins.