Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Content Delivery Network/ Troubleshooting/ Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?

Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?

Updated on 2024-06-06 GMT+08:00

Status Code 403

If the status code 403 is returned, locate the fault as follows:

  1. Check whether your origin server can be accessed. For details, see How Do I Check Whether an Access Fault Is Caused by a CDN PoP or Origin Server?
  2. Check whether the CNAME record matches your acceleration domain name. For details about how to configure the CNAME record, see Configuring a CNAME Record.

  3. If you have configured referer validation, check whether your request URL is allowed by the referer validation rule. CDN identifies and filters out visitors based on a referer blacklist or whitelist. Unqualified users will receive a 403 error response. For details about the rules, see Referer Validation.
  4. If your origin server is an OBS bucket, check whether you have configured a referer whitelist on the origin server and specified that blank referers are not allowed, but no referer validation settings are configured on CDN. If the original request does not carry referer information, CDN will not carry any referer information during origin pull. In this case, origin pull fails and the origin server returns status code 403. To fix this fault, modify the referer validation rule in OBS. For details, see Referer Validation.
  5. If your origin server is an OBS private bucket and OBS authorization is not enabled on CDN, 403 will be returned. Enable OBS authorization on CDN. For details, see OBS Authorization.
  6. If you have configured an IP address whitelist or blacklist, check if your IP address is in the blacklist or is not in the whitelist. If it is in the blacklist or is not in the whitelist, your request will be rejected and a 403 status code will be returned. For details, see IP ACL.
  7. If you have configured a User-Agent blacklist or whitelist, check if your request URL is in the blacklist or is not in the whitelist. If it is in the blacklist or is not in the whitelist, your request will be rejected and a 403 status code will be returned. For details, see User-Agent ACL.
  8. If you have configured token authentication, check the validity period of the signed URL. If the URL has expired, your access to it will be rejected and a 403 status code will be returned. For details, see Token Authentication.

Status Code 404

If the status code 404 is returned, locate the fault as follows:

  1. Access the URL of the origin server and check whether 404 is returned. For details, see How Do I Check Whether an Access Fault Is Caused by a CDN PoP or Origin Server?
  2. If the origin server can be accessed, log in to the CDN console and check whether the host header is correct on the Basic Settings tab of the domain name. For details, see Host Header.
    The differences between the origin server and the host are as follows:
    • The origin server decides the IP address to be accessed during origin pull.
    • The host decides the site that is associated with the requested content.

      Let's assume that the origin server IP address is x.x.x.x, the acceleration domain name is www.example.com, and sites www.a.com and www.b.com are deployed on the origin server.

      • If you want CDN to pull content from the origin server, set the origin server to x.x.x.x on CDN.
      • By default, the host is the acceleration domain name www.example.com. If you want CDN to pull content from the www.a.com or www.b.com site, set the host to www.a.com or www.b.com.
    NOTE:
    • If the origin server is an OBS bucket, the host must be the domain name of the OBS bucket.
    • If your origin server is an object storage bucket of a third party, change the host to the bucket domain name.
  3. Check whether the origin server configuration is correct on the Basic Settings tab of the domain name on the CDN console. If not, correct the IP address or domain name of the origin server.

Status Code 405

Symptom: Content of a domain name with CDN acceleration enabled cannot be accessed. Status code 405 is displayed on the Headers tab under Network of the DevTools when you press F12 on the browser.

Cause: The response header does not support the POST method.

Solution: Edit the HTTP header configuration. Add a rule whose Parameter is Access-Control-Allow-Methods and Value is POST. For details, see HTTP Header Settings (Cross-origin Requests).

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback