0048-00000109

Updated at:

Problem description

When you access an object from a browser using an OSS acceleration endpoint, the browser may download the object directly instead of previewing it.

Cause

For buckets that have transfer acceleration enabled after 18:00 on January 8, 2021, OSS adds two headers to the response when you use an OSS acceleration endpoint to access any object:

x-oss-force-download: true
Content-Disposition: attachment

When a standard browser encounters the Content-Disposition: attachment header, it downloads the object instead of previewing it.

Example problem

For example, a bucket has transfer acceleration enabled after 18:00 on January 8, 2021. The bucket contains an object named test. When you use a browser to access the object with the OSS acceleration endpoint, OSS adds the preceding two headers to the response. A standard browser downloads the object instead of previewing it when it encounters the Content-Disposition: attachment header.

GET /test HTTP/1.1
HTTP/1.1 200 OK
Content-Disposition: attachment
x-oss-force-download: true

Solution

If you do not want OSS to return the force-download headers, you can use a custom domain name to access the object. For more information, see Map custom domain names.