- Introduction to KooGallery
-
Seller Guide
- Registration
- Joint Operations Certification and Product Access
-
Delivery Methods
- Product Release Description
- Delivery Methods
- Image Release Guide
- Releasing Professional Services
- SaaS Release Guide
- Releasing Consulting Services
- License Release Guide
- Releasing Multi-SKU Product Specifications
- Seller Management
- Product Management
- Service Supervision
- Transaction Management
- Settlement Management
- Bill Management
- Issuing Invoices to Huawei Cloud
-
FAQs
- What Enterprise Certificates Are Needed for the Registration?
- Can I Use the Same Account to Apply for Seller Registration Again After I Exit KooGallery?
- How Do I Become a KooGallery Partner?
- How Long Does It Take to Review the Registration Application?
- How Do I Release Products on KooGallery?
- How Long Does It Take to Review a Product Release Application?
- How Do I Remove a Product from the Catalog?
- When Can I Receive the Payment After a Bill Is Generated?
- When Can I Issue an Invoice for an Order?
- Is the Product Technical Support Provided by Sellers or Huawei Cloud?
- How Long Is the Validity Period of Products on KooGallery?
- How Do I Initiate an Appeal During Service Supervision?
- Can an Individual User Become a Seller on KooGallery?
- What Benefits Can I Obtain After Registering with KooGallery?
- Do I Need to Pay Deposit If I Register with KooGallery?
- How Do I Change the Company Name?
- Why Is No Bill Generated for an Order? What Are the Prerequisites for Bill Run?
- How Do I View the Sharing Ratio of a Product?
- How Do I Release a Trial SaaS Specification?
- Why Can't I Select an Image as an Image Asset?
- Reseller Guide
-
User Guide
- Support You May Need
- Huawei Cloud KooGallery Terms
- Product Purchase
- Product Use
- Service Supervision
- After-Sales Support
- Renewal Management
- Product Unsubscription
- Invoice Management
- Agencies
-
FAQs
- What Is Huawei Cloud KooGallery?
- What Software and Services Are Provided on KooGallery?
- How Do I Purchase Cloud Applications on KooGallery?
- Why Can't I Use the Pay-per-Use or Yearly/Monthly Billing Mode for Certain Products?
- How Do I View Purchased Applications?
- How Do I Request Invoices After Purchasing Products from KooGallery?
- What Do I Do If I Encounter a Problem When Using a Product?
- How Do I Renew Purchased Applications?
- What Do I Do If No Applications or Services Meet My Requirements?
- How Do I Contact a Seller?
- What Do I Do If I Cannot Contact a Seller?
- Does Huawei Cloud Support Login Through Third-Party Website?
- Common Problems About Yearly/Monthly Images
- Common Problems About Pay-per-Use Images
- How Do I Initiate an Appeal During Service Supervision?
-
Access Guide
- SaaS Access Guide V2.0 (New Products)
- SaaS Access Guide V1.0 (Existing Products)
- Automatic Deployment and Access Guide
- General Reference
Copied.
Constructing a Request
A request consists of three parts: a request line, request header, and request body (optional).
Request Line
A request line starts with the request method, which is followed by the uniform resource identifier (URI) and protocol version. The request method and URI are separated by a space. The request line format is as follows:
Method Request-URI HTTP-Version CRLF
- Method: request method. All methods are capitalized and their meanings are as follows:
- GET: obtains the resource identified by the Request-URI.
- POST: suffixes new data to the resource identified by the Request-URI.
- PUT: stores a resource identified by the Request-URI.
- DELETE: deletes the resource identified by Request-URI.
- Request-URI: uniform resource identifier.
A combination of different query conditions can be added at the end of the URI by using question marks (?) and ampersands (&). The content contained in {} in the URI is the parameters of the URI, where ? is contained. The part preceding ? is the path parameter, and the part following ? is the query parameter. HTTP-Version: version of the HTTP protocol used by a request.
- CRLF: carriage return and line feed characters. CRLF is placed only at the end of a line. CR and LF must be present at the same time.
Request Header
A request header consists of several fields, each including a domain name, colon (:), and field value. For details, see Common Request Header Fields.
Request Body
A request body is a JSON-based, nested key:value pair. The mandatory and optional fields of an HTTP request body vary depending on the URI.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot