Missing CORS headers for loop monitor REST

[ShahanaFarooqui]

Loop version 0.4.0-beta

Loop monitor REST GET api at 'http://localhost:8081/v1/loop/monitor' is throwing CORS errors:

[ShahanaFarooqui]

@guggero I am receiving the same error with v0.4.1 as well. But, all other APIs, except monitor, are working on REST without any error.

v0.4.1:

Error:

[guggero]

Hmm... I probably shouldn't have exposed an URL for the monitor call, the streaming mechanism works differently from the other calls and is not really user friendly with REST. Is there anything missing in the synchronous calls (/v1/loop/swaps or /v1/loop/swap/<hash>)? Or did you just want to use the monitor stream for performance reasons?

[ShahanaFarooqui]

We want to show streamed/live updates from monitor on the UI.

[saubyk]

@guggero agree with you.
The swaps and swap apis are good for us to meet the requirements of the user interface.

Monitor api is not a good solution for the UI anyway as I have already raised in the below issue:
#126

[ShahanaFarooqui]

@guggero looks like /v1/loop/swap/<hash> api is not decoding the route parameter (id), which can contain "/". We opened another issue #154 with details.