Open curtishall opened 9 years ago
Possibly will get fixed with a commit 2604befbf443c05f6fecbfc19138a9d060b5783a (Include https support in FFmpeg libs). Will provide a build shortly.
Actually, to support MJPEG via HTTPS, we need to store the chosen URL schema (HTTP or HTTPS) in Devices entry, let's say, in mjpeg_path
field, which currently consists of hostname, port and resource path. We could add schema as first field here, and handle previously configured devices in DB with an upgrade script. Also an heuristic algorithm could be added to handle entries without this new fourth field (consider data restored from DB backup): if field doesn't start with "http", then assume it is in old format and contains three fields; assume "http" schema.
@antonsviridenko any comments?
My only concern is backwards compatibility for existing devices, but it sounds like customers who are using http won't have to change anything
Customers may want SSL for MJPEG streaming. This will require changes to the web UI and server.