Skip to main content

Overview

CloudBase provides a unified HTTP Access Service, enabling developers to easily access various cloud resources within the environment through standard HTTP protocols. This eliminates the need for complex SDK integration while facilitating the invocation and management of backend cloud resources.

HTTP Access Service supports extensive custom configurations, including advanced capabilities such as resource access path (URL Path) customization and access service domain name (CNAME) configuration, comprehensively meeting personalized requirements across diverse development scenarios.

Core Features and Advantages​

  • High-Performance Access Experience: Based on optimized HTTP protocol implementation, it delivers low-latency, high-concurrency resource access capabilities
  • Flexible Routing Configuration: Supports granular routing rule configuration for domain names and access paths, enabling intelligent distribution of requests
  • Custom Domain Management: Supports custom binding/unbinding of domains, enabling access to environment services through personalized domains to enhance brand recognition
  • Multi-Protocol Support: Fully supports HTTP/HTTPS protocol standards, compatible with various clients and browsers

Default Domain Name​

CloudBase provides a free domain by default for each environment. However, based on security and compliance requirements, the default domain is only suitable for the development and testing phase and has the following limitations:

  • Access Frequency Limit
  • Some advanced features are unavailable
  • Stability risks may exist

After October 9, 2025, default domains for newly created environments (including Cloud Run, Static Web Hosting, and HTTP Access Service) will be subject to additional restrictions:

  • Default domains (including those for Cloud Run, Static Web Hosting, HTTP Access Service, excluding Cloud Storage) will validate validity for browser-direct access requests (where the Sec-Fetch-Mode header value is 'navigate'), and add the Content-Disposition: attachment response header to other requests (triggering download prompts when opened directly in browsers)
  • For expired default domain names, users can click Apply in the console to automatically renew them

For production environments, it is strongly recommended to bind custom domains that have completed ICP filing to obtain full service capabilities and stability guarantees. If you need to directly access Static Web Hosting, Cloud Run, or HTTP Access Service via browsers (excluding API calls or resource access like images), custom domains must be used in production environments.

Please refer to Custom Domain Configuration to configure a custom domain.

Domain-Resource Association Capability​

HTTP Access Service supports binding multiple cloud resources to a domain, including:

  • Cloud Function (CloudFunction)
  • Cloud Run (CloudRun)
  • Static Website Hosting (Hosting)
  • WeDa Application

Through resource association configuration, you can access different types of cloud resources via a unified HTTP method, simplifying application architecture design.

Advanced Configuration Options​

HTTP Access Service provides comprehensive advanced configuration capabilities:

  • Trigger Path Selection: Customize resource access paths to implement RESTful API-style interface design
  • Authentication: Enable access control for sensitive resources to ensure data security.
  • Path Passthrough: Supports passing the complete request path to backend services, facilitating the implementation of complex routing logic
  • Request Parameter Configuration: Customize request parameter processing rules to meet the requirements of different business scenarios
  • Response Header Management: Configure custom response headers to enhance frontend interaction experience

Through these advanced configurations, you can flexibly control resource access methods and security policies, building a professional cloud service architecture that meets business requirements.