…ich has no effect.
This is only currently used to manage logins for the WebFrontend and it isn't a complete implementation but it could be extended in future to support multi-user features. There is no UI yet to add/remove users, set passwords or permissions. The design is session based, with the master backend acting as the central, and only, manager for sessions. Users log in on any client, but the actual request is processed on the master. A successful login results in the creation of a 'session' identified with a session token which the client will use in all subsequent exchanges to minimise the login credentials going over the network. Sessions have expiry dates and can be terminated at the master backend effectively allowing users to be 'logged out' remotely. For the WebFrontend sessions end when the browser is closed, unless TLS is being used in which case a cookie is set which allows the session to be resumed. There is a stub for a context-dependent permissions system, extensible by plugins. Other multi-user features such as restricting usage for certain users to a set period during the day, or a fixed number of hours can be bolted on later.
…to get it to work
…several dvb-s2 multiplexes across Europe
Previously, the invalid value "0000-00-00 00:00:00" was used for MythDates that were not applicable. With Qt5, invalid values get translated to NULL when saving to the database and this causes an error if the column is not configured to allow NULLs. This commit changes the affected columns in the record table and the supporting code to allow NULLs.
This changes the cetonstreamhandler code from using QHttp to MythDownloadManager. This is needed for Qt5, but is backwards compatible for the current Qt4.8 distributions. Fixes #12067 Signed-off-by: David Engel <email@example.com>
Fixes #12381 Signed-off-by: David Engel <firstname.lastname@example.org>
If m_reload is true, request that Qt actually performs similiarly to a browser reload (bypass and reload any cache). Fixes #12066 Signed-off-by: David Engel <email@example.com>
If the QNetworkRequest has a CacheLoadControlAttribute of AlwaysNetwork, set the reload flag for a post and queuePost request. While posts are usually not cached, the RFCs allow it in specific cases. This allows the caller to request no cache processing. Refs #12066 Signed-off-by: David Engel <firstname.lastname@example.org>
If the QNetworkRequest has a CacheLoadControlAttribute of AlwaysNetwork, set the reload flag for a download and queueDownload request. Refs #12066 Signed-off-by: David Engel <email@example.com>