OCS/config values are hardcoded

[SamuAlfageme]

I was looking around the OCS API once again and noticed:

core/lib/private/OCS/Config.php

Lines 29 to 36 in e0cde94

	public static function apiConfig() {
	$xml['version'] = '1.7';
	$xml['website'] = 'ownCloud';
	$xml['host'] = \OCP\Util::getServerHost();
	$xml['contact'] = '';
	$xml['ssl'] = 'false';
	return new Result($xml);
	}

... this causes some hardcoded values to be returned on the ocs/config endpoint:

$ curl -X GET 'http://localhost/ocs/v1.php/config?format=json' -u 'admin:admin'

{
    "ocs": {
        "meta": {
            "status": "ok",
            "statuscode": 100,
            "message": null
        },
        "data": {
            "version": "1.7",
            "website": "ownCloud",
            "host": "localhost",
            "contact": "",
            "ssl": "false"
        }
    }
}

I guess:

• website - specially for branded versions.
• contact
• ssl

... should also be dynamically generated from e.g. config.php.

[DeepDiver1975]

The whole Route can be removed

[SamuAlfageme]

@DeepDiver1975 sync client relies on this route for owncloud/client@b0f986c#diff-25fa7af0e8c67974874ead6e9eb2d29c (i.e. if overwritehost was set) - do we have an alternative for this?

[DeepDiver1975]

🧚

[individual-it]

related to #34664 ?