Docs

Torch Object Storage

Announcements

Announcement on Enabling URL Encoding for Object Names in Torch Object Storage Log Storage

To enhance our services, Volcano Engine Torch Object Storage (TOS) will implement URL encoding for object names in log files created through the log storage feature starting December 1, 2025.

Estimated Change Time

2025-12-1 (Beijing Time). Please refer to the console for the specific time.

Change Description

You can use the log storage feature to save access log files directly to a specified bucket for auditing and reconciliation purposes. TOS will URL encode the field related to object names (i.e., Object) in log files. The changes are explained below.

Before the change: Object names were saved in their original format in log files, without any encoding. For example, the data/file/日志存储.txt file appears in the log file as:

"2025-07-26T16:07:19.464+08:00","data/file/日志存储.txt","bucketName"

After the change: TOS applies URL encoding to object names in log files, in accordance with the RFC 3986. For example, the data/file/日志存储.txt file appears in the log file as:

"2025-07-26T16:07:19.464+08:00","data%2Ffile%2F%E6%97%A5%E5%BF%97%E5%AD%98%E5%82%A8.txt","bucketName"

Moreover, TOS introduces the LogVersion field, which specifies the encoding method used for object names in the log file. The values are described as follows:

1.0: Object names in the log file are not encoded.

2.0: Object names in the log file are URL encoded.

Impacts

If the log storage feature is enabled on your bucket before December 1, 2025, the object names in the log files will remain unencoded and in their original format. This change will not affect them. However, if you need to URL encode those object names, submit a ticket or contact your account manager for assistance.

If the log storage feature is enabled on your bucket on or after December 1, 2025, the object names in the log files will be URL encoded by default. Add a URL decoding step to your program if it needs to read object names in their original format to avoid parsing errors caused by encoded characters. For instructions, see Examples of decoding object names.

If you have any questions about the changes, submit a ticket or contact your account manager for assistance.

Last updated: 2025.10.30 18:52:24