Change Details

When downloading content blobs via the API (e.g, from [[ https://archive.softwareheritage.org/api/1/content/sha1:adc83b19e793491b1c6ea0fd8b46cd9f32e592fc/raw/ | this URL ]]), the download file name proposed by the browser is horrible, which is expected in the general case. However, in specific cases people might want to link to Software Heritage download URLs, specifying themselves the desired file name. We need to add the ability to specify the desired download file name when linking to /raw/ download URLs. As a first approximation, this might take the form of a `?filename=...' GET parameter.

When downloading content blobs via the API (e.g, from [[ https://archive.softwareheritage.org/api/1/content/sha1:adc83b19e793491b1c6ea0fd8b46cd9f32e592fc/raw/ | this URL ]]), the download file name proposed by the browser is horrible, which is expected in the general case. However, in specific cases people might want to link to Software Heritage download URLs, specifying themselves the desired file name. We need to add the ability to specify the desired download file name when linking to /raw/ download URLs. As a first approximation, this might take the form of a `?filename=...` GET parameter.

When downloading content blobs via the API (e.g, from [[ https://archive.softwareheritage.org/api/1/content/sha1:adc83b19e793491b1c6ea0fd8b46cd9f32e592fc/raw/ | this URL ]]), the download file name proposed by the browser is horrible, which is expected in the general case. However, in specific cases people might want to link to Software Heritage download URLs, specifying themselves the desired file name. We need to add the ability to specify the desired download file name when linking to /raw/ download URLs. As a first approximation, this might take the form of a `?filename=...'` GET parameter.