Skip to main content

Frequently Asked Questions

Access Issues​

What causes a 514 error when accessing static resources?​

When a 514 error occurs while accessing statically hosted resources, it is typically caused by triggering the IP access frequency limit configuration.

Root Cause Analysis:

IP access frequency limiting applies to the total number of requests for statically hosted resources, rather than the number of requests for individual files. When a user accesses a webpage, the browser simultaneously requests all static resources on the page (HTML, CSS, JS, images, etc.), each of which contributes to the access frequency statistics for that IP.

Specific Scenarios:

Assume your web page contains:

  • 1 HTML file
  • 3 CSS files
  • 5 JS files
  • 10 image files

When a user accesses the page, 19 concurrent requests will be generated. If the IP access frequency limit is set to 2 QPS, 17 requests will be denied, returning a 514 error.

Solution:

  1. Check the number of page resources

    • Use browser developer tools to view the number of network requests
    • Count the total number of resources during page loading

  2. Adjust the QPS settings

    • Go to Cloud Development Console → Environment Configuration → Security Control → Static Hosting Security Configuration
    • Set the QPS threshold to 1.5-2 times the number of page resources
    • For example: If a page has 20 resources, it is recommended to set the QPS to 30-40

  3. Configure by page type

    • Simple pages (5-10 resources): Recommended QPS 20-30
    • Regular websites (15-30 resources): Recommended QPS 50-80
    • Rich media pages (50+ resources): Recommended QPS 100-200

⚠️ Note: Setting an excessively low QPS limit may affect normal users' page loading experience. It is recommended to configure it properly based on actual business requirements.