tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

POST Object Common Exceptions

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-11-06 17:05:28

Symptoms

When POST requests are initiated via COS APIs, the following error messages are returned:

Troubleshooting

Error message "Condition key q-ak doesn't match the value XXXXXX"

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>AccessDenied</Code>
<Message>Condition key q-ak doesn&apos;t match the value XXXXXX</Message>

Possible cause

q-ak parameter input error.

Solution

1. Log in to the CAM console and go to the Manage API Key page to view the key information.
2. Check whether the q-ak parameter is incorrectly set based on the key information:
Yes: change the value of the q-ak parameter to the correct SecretId.

Error message "You post object request has been expired, expiration time: 1621188104 but the time now : 1621245817"

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>AccessDenied</Code>
<Message>You post object request has been expired, expiration time: 1621188104 but the time now : 1621245817</Message>

Possible cause

The value of expiration in the policy has expired.

Solution

Change the value of expiration in the policy.
Note:
The value of expiration must be later than the current time. The recommended value is a time 30 minutes later than the current time (UTC time).

Error message "The Signature you specified is invalid."

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>SignatureDoesNotMatch</Code>
<Message>The Signature you specified is invalid.</Message>

Possible cause

Signature calculation error.

Solution

Check whether the POST signature string generation rule is correct by referring to Request Signature :

Error message "You must provide condition if you specify a policy in post object request."

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>InvalidPolicyDocument</Code>
<Message>You must provide condition if you specify a policy in post object request.</Message>

Possible cause

Policy format error.

Solution

Change the policy format to the standard JSON format by referring to POST Object.

Error message "Condition key bucket doesn&apos;t match the value [bucket-appid]"

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>AccessDenied</Code>
<Message>Condition key bucket doesn&apos;t match the value [bucket-appid]</Message>

Possible cause

The bucket in the policy is inconsistent with that in the request.

Solution

Use the bucket specified in the policy to initiate the request.

Error message "Condition key key doesn&apos;t match the value XXXXX"

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>AccessDenied</Code>
<Message>Condition key key doesn&apos;t match the value XXXXX</Message>

Possible cause

The uploaded content does not comply with the policy.

Solution

Upload content that meets the conditions specified in the policy.

Error message "The body of your POST request is not well-formed multipart/form-data."

When POST requests are initiated via COS APIs, the following information is displayed:
<Code>MalformedPOSTRequest</Code>
<Message>The body of your POST request is not well-formed multipart/form-data.</Message>

Possible cause

The POST body format is invalid.

Solution

Correct the body format by referring to POST Object.

Ajuda e Suporte

Esta página foi útil?

comentários