Re: [EME] Should we validate defaultURL/destinationURL?

Requiring the UA to validate the URLs passed would be a problem. The use cases that I outlined for allowing the CDM to exchange information directly with the application would rely on non-standard URL schemes. So we could either standardize the scheme used as I suggested (e.g. app://example.com/<path+params>) or not require these URLs to be standardized.

Joe Steele
steele@adobe.com<mailto:steele@adobe.com>

On Dec 7, 2012, at 11:01 AM, David Dorwin <ddorwin@google.com<mailto:ddorwin@google.com>> wrote:

Both versions of the API just say that defaultURL/destinationURL is a DOMString. There is no mention of validating it or that it must be a valid URL. Should we add such language?

It should be easy enough for the UA to validate the URLs before passing them to the client, and then the application doesn't need to worry about it. This also prevents this field from being abused for other purposes. The only downside I can think of is that invalid URLs would not be passed to the app, and it would have no indication that a URL was provided.

David