0026-00000012
Description
The object file that the symbolic link points to does not exist.
Cause
This error occurs when you try to access a symbolic link, but its target object file does not exist.
Sample Problem
For example, you send the following request:
HEAD /link-to-nothing HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Date: Wed, 02 Jan 2019 13:28:38 GMT
Authorization: OSS qn6q**************:77Dv****************If link-to-nothing in the request is a symbolic link and the object file it points to does not exist, this error is returned.
Solution
You can use the GetSymlink operation to view the path of the object file that a symbolic link points to. For example:
GET /link-to-nothing?symlink HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Date: Wed, 02 Jan 2019 13:28:38 GMT
Authorization: OSS qn6q**************:77Dv****************A response similar to the following example is returned:
HTTP/1.1 200 OK
Server: AliyunOSS
Date: Wed, 02 Jan 2019 13:28:38 GMT
Last-Modified: Wed, 01 Jan 2019 13:28:38 GMT
Content-Length: 0
Connection: keep-alive
x-oss-request-id: 5650BD7****FB30443962F9A
x-oss-symlink-target: file-not-exist
ETag: "A797938C31D59EDD08D86188F6D5****"The x-oss-symlink-target field indicates that the link-to-nothing file points to the file-not-exist object file. If an object file named file-not-exist does not exist in the bucket, a call to the HeadObject operation on link-to-nothing returns this error. Ensure that the object file targeted by the symbolic link exists.