Requirement:
In multi-language environments, the AUT client sends the installed client language in the XML request after the language information is available in the registry.
Currently, the server returns an update only when the version map contains an entry matching the requested language. If there is no exact language match, the server returns no update found.
The requested enhancement is to provide an option for a language-independent update fallback. When the client requests an update for a specific language and no exact language match exists in the version map, the server should be able to deliver a language-independent update configured by the administrator.
Business/Operational Impact:
In environments with multiple client languages, administrators currently need to maintain separate version path/version map configurations and upload the corresponding AUTCatalog and HTTP filesystem content for each language. This results in additional administrative effort, configuration overhead, and duplication of files and disk space.
A language-independent fallback would allow a single update configuration to be used when no exact language-specific match is available, while still allowing language-specific updates to be configured where required.
Expected Behavior:
If an exact language match exists, the language-specific update should be delivered.
If no exact language match exists and a language-independent update is configured, the language-independent update should be delivered.
If neither a matching language-specific update nor a language-independent update is available, the server should return no update found.
