The file is still being saved as .ova but macOS is associating it as OVF format because of the virtualisation software that is installed on macOS like VMWare Fusion. Here's the screenshots
With VMWare installed there is a default file association that is happening. Its the same with Chrome and Brave
File name is still .ova but the kind of file association is OVF
Hello there, if you try to do it again with AWS S3, Brave will save OVA file as ".OVF" file. There is a dependency on AWS S3 responses somehow. I would ask to investigate this further, by replicating the problem with Brave and AWS S3.
More details on the issue, according to my results these are important points for reproducing it:
Brave browser connecting to AWS S3 for OVA download
"Content-Disposition" used in the request with "attachment; "+filename+".ova" (usually different from the file stored in S3, this is essential in reproducing!) specified in the "Content-Disposition", where "Content-Type" is defined as "application/gzip", "binary/octet-stream", others (with no effect)
It appears that Brave doesn't set/use the filename passed in the request/response for saving it correctly as ".ova", but rather uses the virtualization file extensions set in the OS (e.g. MacOS).
Workaround: The workaround at this points (until the fix is implemented in Brave) is to not specify filename in the "Content-Disposition", in which case the file is saved with ".ova" extension, as one would expect.