URL signing - 403 error not handled by player
We are trying to implement URL signing and we are wondering how the player handles expired URLs. Let's say a video URL expires in 10min and the user switches to another quality after these 10mins. Then this video url will have expired and it will fail playing. Or if the user doesn't start the video immediately but 8min later and if he changes the quality after 2min, then it would fail too.
Also the JS API on('error') callback does not provide the error code but a generic error object instead so we have no way to tell if the error was caused by a permission issue or something else.
Finally let's assume that the video urls expired and we hack our way around the API, load new video urls and provide them to the player. The player would play these videos from the start and not from where the user stopped playing the video, wouldn't it?
It seems that the docs are lacking information on that subject and we are unsure on how to approach that problem!
Any help would be really appreciated!