Ok, the feedback I’m getting is that the File Pre-Cache Wizard never handled the FireFox download links. The issue is that those links are inside of a relevance substitution, which should be evaluated on the client itself (this way the client only downloads the specific language-version that it needs).
Inside the relevance substitution, the URL download strings are percent-encoded, as necessary when defining the string in Relevance. In all the places where the literal URL needs a space, the space is URL-encoded to the ‘%20’ symbol to represent a space; and then further Relevance percent-encoded to ‘%2522’ to represent “literal percent-symbol followed by 22”. The File Pre-Cache Wizard does not perform the relevance substitutions on the URL and tries to include the literal %25 as part of the URL, so it’s a bad download link.
It’s not clear whether the File Precache Wizard could be enhanced to handle every case of relevance substitutions (since those should be done on the client, and conceivably could have things like ‘OS’ or installed application checks), but maybe these very trivial substitutions could be handled in some cases.
I’ve added an Idea at https://bigfix-ideas.hcltechsw.com/ideas/BFP-I-365 to enhance the precache wizard to try to handle those URLs. Please upvote if this is important to you.
