All Products
Search
Document Center

Object Storage Service:0017-00000134

Last Updated:Mar 20, 2026

The x-oss-user-last-modified request header contains an invalid date value — the value is at or before the Unix epoch (1970-01-01 00:00:00 UTC).

Problem description

The date value provided for the x-oss-user-last-modified request header is invalid.

Causes

OSS uses UNIX timestamps internally, which start at 1970-01-01 00:00:00 UTC. Any value set for x-oss-user-last-modified must be strictly later than that point in time. Values at or before 1970-01-01 00:00:00 UTC are rejected.

Examples

The following request triggers the error because x-oss-user-last-modified is set to exactly the Unix epoch:

PUT /example-object.txt HTTP/1.1
Host: example-bucket.oss-cn-hangzhou.aliyuncs.com
Date: Mon, 20 Mar 2024 10:30:00 GMT
x-oss-user-last-modified: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 1234
Authorization: OSS LTAI****************:miAo****************

[Object Content]

OSS returns a 400 Bad Request response:

HTTP/1.1 400 Bad Request
Server: AliyunOSS
Date: Mon, 20 Mar 2024 10:30:00 GMT
Content-Type: application/xml
Content-Length: 534
Connection: keep-alive
x-oss-request-id: 68C05BB8785D7A3133226E20
x-oss-server-time: 0
x-oss-ec: 0017-00000134

<?xml version="1.0" encoding="UTF-8"?>
<Error>
  <Code>InvalidArgument</Code>
  <Message>Invalid date. Must be later than 1970-01-01 00:00:00.</Message>
  <RequestId>68C05BB8785D7A3133226E20</RequestId>
  <HostId>example-bucket.oss-cn-hangzhou.aliyuncs.com</HostId>
  <ArgumentName>x-oss-user-last-modified</ArgumentName>
  <ArgumentValue>Thu, 01 Jan 1970 00:00:00 GMT</ArgumentValue>
  <EC>0017-00000134</EC>
  <RecommendDoc>https://api.aliyun.com/troubleshoot?q=0017-00000134</RecommendDoc>
</Error>

The <ArgumentName> and <ArgumentValue> fields in the response identify the invalid header and the submitted value. Use these fields in error-handling logic to pinpoint which parameter caused the failure, and include them in error logs to speed up diagnosis.

Solutions

If you don't need to set a custom last-modified time, omit the x-oss-user-last-modified header entirely. OSS will use the actual time of the upload or modification.

If you do need to set the header, use a date that is later than 1970-01-01 00:00:00 UTC and follows the HTTP date format defined in RFC 2616 (for example, Wed, 15 Mar 2024 08:20:30 GMT).

The following request shows a valid header value:

PUT /example-object.txt HTTP/1.1
Host: example-bucket.oss-cn-hangzhou.aliyuncs.com
Date: Mon, 20 Mar 2024 10:30:00 GMT
x-oss-user-last-modified: Wed, 15 Mar 2024 08:20:30 GMT
Content-Length: 1234
Authorization: OSS LTAI****************:miAo****************

[Object Content]

Requirements for a valid x-oss-user-last-modified value:

  • The date must follow the HTTP date format (RFC 2616), such as Wed, 15 Mar 2024 08:20:30 GMT.

  • The date must be later than 1970-01-01 00:00:00 UTC.

References