Allowing custom URI scheme for CORS allowed origin list

[AndersRod]

Is your feature request related to a problem? Please describe.

I am trying to add 'ionic://localhost' to the CORS allowed origin list of the Azure SignalR resource, but this is getting blocked by the validator (both on the Portal and through AZ CLI as well).

Describe the solution you'd like

Custom URI schemes for CORS allowed origin list to be allowed.

Additional context

I am working on an Ionic app for iOS (via WebView) with the @microsoft/signalr ts client library. http | https are reserved schemes on iOS, which is why the Ionic app uses ionic as the URI default scheme. The Azure Portal as well as the AZ CLI for SignalR validates the CORS origin allowed list entries based of the following format: [HTTP|HTTPS]://[www.]domain.[TLD][:portnumber].

Would it be possible to relax the schema part of the URI validation - so custom schemas are allowed?

A current workaround is to use '*' to allow all origins. Alternatively I will have to port the @microsoft/signalr ts client library to Cordova to do native http requests.

[roopeshchinnakampalli]

Any luck on this issue?