vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Valid values for ciphers are ECDHE-ECDSA-AES128-GCM-SHA256, ECDHE-ECDSA-CHACHA20-POLY1305, ECDHE-RSA-AES128-GCM-SHA256, ECDHE-RSA-CHACHA20-POLY1305, ECDHE-ECDSA-AES128-SHA256, ECDHE-ECDSA-AES128-SHA, ECDHE-RSA-AES128-SHA256, ECDHE-RSA-AES128-SHA, AES128-GCM-SHA256, AES128-SHA256, AES128-SHA, ECDHE-ECDSA-AES256-GCM-SHA384, ECDHE-ECDSA-AES256-SHA384, ECDHE-RSA-AES256-GCM-SHA384, ECDHE-RSA-AES256-SHA384, ECDHE-RSA-AES256-SHA, AES256-GCM-SHA384, AES256-SHA256, AES256-SHA, DES-CBC3-SHA, default. For example: -v AES256-SHA256,AES256-SHA, using -v default to reset configured cipher suites to default value.



-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Enable tls_client_auth for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis domain-settings-update -f tls_client_auth -v on 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"









 Edge functions 

Manipulate how Edge Functions perform using the following edge-functions commands:



 ibmcloud cis edge-functions-actions
route add -net 166.9.0.0/16 gw <gateway> dev <gateway_interface>

Replace <gateway> (for example, 10.x.x.x) and <gateway_interface> (for example, eth10) with the appropriate values.
2. Optional: Verify that the route was added successfully by displaying your new routing table.

route -n







 Step 2. Target the CIS private endpoint 

After you configure your virtual server instance to accept IBM Cloud private network traffic, you can target the private endpoint for CIS by using the CIS API or CIS CLI plug-in.



1. In a terminal window, log in to IBM Cloud.

ibmcloud login

If the login fails, run the ibmcloud login --sso command to try again. The --sso parameter is required when you log in with a federated ID. If this option is used, go to the link listed in the CLI output to generate a one-time passcode.
2. Optional: Ensure that your account is enabled for VRF and service endpoints.

ibmcloud account show

The following CLI output shows the account details of a VRF and service endpoint-enabled account.

Retrieving account John Doe's Account of john.doe@email.com...
OK

Account ID: d154dfbd0bc2edefthyufffc9b5ca318
Currently Targeted Account: true
Linked Softlayer Account: 1008967
VRF Enabled: true
Service Endpoint Enabled: true

To learn how to set up your account for connecting to a private network, see [Enabling VRF and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint).







 Step 3. Create a CIS resource on the private network 

Test your private network connection by using the [CIS CLI plug-in](https://cloud.ibm.com/docs/cis-cli-plugin?topic=cis-cli-plugin-cis-cli).



1.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-page-rule" "> --><-- <section "id="section-command-examples-page-rule" "> --> Examples Get details of page rule a5836c2a7ea72d2e225890caea70ae32. ibmcloud cis page-rule 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo --output JSON
<-- </section "id="section-command-examples-page-rule" "> --><-- </section "id="section-page-rule" "> --><-- </section "id="section-page-rule-cli-ref" "> --><-- <section "id="section-range-app" "> --> Range app Manipulate how the Range App performs using the following range-app commands:<-- <section "id="section-create-range-app" "> --> ibmcloud cis range-app-create Create a new range application (Enterprise plan only). ibmcloud cis range-app-create DNS_DOMAIN_ID --name NAME --edge-port EDGE_PORT --origin-direct ORIGIN_DIRECT --origin-direct ORIGIN_DIRECT] --proxy-protocol on|off] --ip-firewall on|off] --edge-connectivity all|ipv4|ipv6] --edge-tls off|flexible|full|strict] --traffic-type direct/http/https] -i, --instance INSTANCE] --output FORMAT]
You can configure global load balancing with a technology such as IBM Cloud® Internet Services (Cloud Internet Services (CIS)). Cloud Internet Services (CIS) provides health checking and routing rules to ensure that API traffic is automatically routed to the nearest healthy region. For more information about global load balancing, see the [Global Load Balancer (GLB) documentation](https://cloud.ibm.com/docs/infrastructure/cis?topic=cis-global-load-balancer-glb-concepts).

For information about high availability and disaster recovery standards in IBM Cloud, see [How IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime). You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeSLAs).
ibmcloud cis tls-settings 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"
<-- </section "id="section-show-tls-setting-examples" "> --><-- </section "id="section-show-tls-setting" "> --><-- <section "id="section-update-tls-settings" "> --> ibmcloud cis tls-settings-update Update TLS settings for a given DNS domain. ibmcloud cis tls-settings-update DNS_DOMAIN_ID --mode MODE] --universal (true|false)] --tls-1-2-only (on|off)] --tls-1-3 (on|off)] -i, --instance INSTANCE]--output FORMAT] !
<-- <section "id="section-update-tls-settings-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--mode: Specify whether visitors can browse your website over a secure connection, and when they do, how CIS will connect to your origin server. Valid values: off, client-to-edge, end-to-end-flexible, end-to-end-ca-signed, https-only-origin-pull. See the following documentation link for detailed TLS mode description]] ! ! ! ! ! .--universal: Specify whether universal ssl is enabled for you domain. Valid values are true and false.--tls-1-2-only: Specify whether Crypto TLS 1.2 feature is enable for your domain. Enabling this feature prevents use of previous versions. Valid values are on and off.--tls-1-3: Specify whether Crypto TLS 1.3 feature is enabled for your domain. Valid values are on, off.--min-tls-version: Only accept HTTPS requests that use at least the TLS protocol version specified.
<-- </section "id="section-update-cis-service-instance-examples" "> --><-- </section "id="section-update-cis-service-instance" "> --><-- <section "id="section-get-cis-service-instance" "> --> ibmcloud cis instance Show details of a CIS service instance. ibmcloud cis instance INSTANCE --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-get-cis-service-instance-options" "> --> Command options INSTANCE: The name or ID of a CIS service instance. Required.--output: Specify output format, only JSON is supported.<-- </section "id="section-get-cis-service-instance-options" "> --><-- <section "id="section-get-cis-service-instance-examples" "> --> Examples Show details of cis instance cis-demo. ibmcloud cis instance cis-demo
<-- </section "id="section-get-cis-service-instance-examples" "> --><-- </section "id="section-get-cis-service-instance" "> --><-- <section "id="section-list-cis-service-plans" "> --> ibmcloud cis plans List all CIS service plans. ibmcloud cis plans --refresh] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-list-cis-service-plans-options" "> --> Command options --refresh: Force refresh from catalog.--output: Specify output format, only JSON is supported.<-- </section "id="section-list-cis-service-plans-options" "> --><-- <section "id="section-list-cis-service-plans-examples" "> --> Examples List CIS services plans. ibmcloud cis plans --refresh
(https://cloud.ibm.com/docs/cis?topic=cis-order-of-execution)
* [Troubleshooting 500 class errors](https://cloud.ibm.com/docs/cis?topic=cis-html-5xx-errors)
* [Troubleshooting 1000 class errors](https://cloud.ibm.com/docs/cis?topic=cis-html-1xxx-errors)
* [How do I generate a HAR file?](https://cloud.ibm.com/docs/cis?topic=cis-generate-har-files)
* [Why is my domain still in Moved status?](https://cloud.ibm.com/docs/cis?topic=cis-domain-moved-status)



* [Getting help and support for CIS](https://cloud.ibm.com/docs/cis?topic=cis-gettinghelp)



* [Go to product UI](https://cloud.ibm.com/catalog/services/internet-services) [About this product](https://www.ibm.com/cloud/cloud-internet-services)



Expand all | Collapse all

Collapse



1. [IBM Cloud Docs](https://cloud.ibm.com/docs)
2. [Cloud Internet Services (CIS)](https://cloud.ibm.com/docs/cis)
3.



Search in collection

Search in collection





LangSwitcher dropdown

English

Close menu

DeutschEnglish

EspañolFrançaisItaliano日本語한국어Português/Brasil简体中文繁體中文





 HTTP concepts * Last updated 2020-12-09 

HTTP/2 and HTTP/3 accelerate page load and are included in all IBM Cloud® Internet Services plans. HTTP/2 is enabled by default and requires an SSL certificate at the CIS edge network. Domains on Trial plans cannot disable HTTP/2.

A browser and web server automatically negotiate the highest protocol available, so HTTP/3 takes precedence over HTTP/2.
ibmcloud cis access-certificate-create 31984fea73a15b45779fa0df4ef62f9b --name example --ca-cert-file CERT_FILE --associated-hostnames example.com -i cis-demo







 ibmcloud cis access-certificates 

List all access certificates for a given DNS domain (Enterprise plan only).

ibmcloud cis access-certificates DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

List all access certificates for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis access-certificates 31984fea73a15b45779fa0df4ef62f9b -i cis-demo







 ibmcloud cis access-certificate 

Show details of an access certificate (Enterprise plan only).

ibmcloud cis access-certificate DNS_DOMAIN_ID ACCESS_CERTIFICATE_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_CERTIFICATE_ID
: The ID of access certificate. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Show details of access certificate a5836c2a7ea72d2e225890caea70ae32.
Valid values: certificate, common_name. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Create access policy for access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-policy-create 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -name examplePolicy --decision non_identity --include certificate --include common_name=test -i cis-demo







 ibmcloud cis access-policies 

List all access policies for a given access application (Enterprise plan only).

ibmcloud cis access-policies DNS_DOMAIN_ID ACCESS_APPLICATION_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

List all access policies for access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-policies 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo







 ibmcloud cis access-policy 

Show details of an access policy (Enterprise plan only).

ibmcloud cis access-policy DNS_DOMAIN_ID ACCESS_APPLICATION_ID ACCESS_POLICY_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options
ibmcloud cis access-policies 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo







 ibmcloud cis access-policy 

Show details of an access policy (Enterprise plan only).

ibmcloud cis access-policy DNS_DOMAIN_ID ACCESS_APPLICATION_ID ACCESS_POLICY_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

ACCESS_POLICY_ID
: The ID of access policy. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Show details of access policy a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-policy 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 65fe21071877669cc69544642bc6c4c4 -i cis-demo







 ibmcloud cis access-policy-delete 

Delete an access policy (Enterprise plan only).

ibmcloud cis access-policy-delete DNS_DOMAIN_ID ACCESS_APPLICATION_ID ACCESS_POLICY_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

ACCESS_POLICY_ID
: The ID of access policy. Required.

-i, --instance
: Instance name or ID.
This allows CIS to deliver a more complete minification result. If you need to enable or disable minification for CSS and JavaScript, purge your CIS cache to see the effect of any minification change.





 Image size optimization compression 

Image size optimization compresses resources cached in the CIS edge network by stripping metadata and applying lossy or lossless compression. Image size optimization accelerates image downloads by reducing image size. Image size optimization cannot optimize off-site resources.

Image size optimization compression is only available as a page rule in the UI. The domain level setting is available in the CLI.



 Image size optimization compression options 

The following sections detail the image size optimization compression options.



 Lossless 

The lossless option attempts to strip most metadata (for example EXIF data), but doesn't change the image detail. Effectively, when uncompressed, a lossless image is identical to the original.





 Lossy 

The lossy option attempts to strip most metadata and compresses images by approximately 15 percent. When uncompressed, some of the redundant information from the original image is lost.

Lossy has the same effect as Lossless when applied to PNG.

With Lossless and Lossy modes, CIS attempts to strip as much metadata as possible. However, there is no guarantee that all metadata is stripped because other factors, such as caching status, might affect which metadata is finally sent in the response.





 WebP 

WebP is a modern image format providing superior lossless and lossy compression for images. WebP lossless images are approximately 26 percent smaller than PNGs, while lossy images are 25 to 34 percent smaller than JPEGs.

Image size optimization creates and caches a WebP version of the image and delivers it to the browser if the Accept header from the browser includes WebP and the compressed image is significantly smaller than the lossy or lossless compression.

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8

Currently, WebP is only supported in Firefox, Google Chrome, and Opera browsers.
Command options 

--name
: Action name (Enterprise plan only).

--javascript-str
: Javascript string. For example: addEventListener('fetch', event => { event.respondWith(fetch(event.request))})

--javascript-file
: Javascript file.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Update an Edge Functions action for instance action-demo.

ibmcloud cis edge-functions-action-update --javascript-str "addEventListener('fetch', event => { event.respondWith(fetch(event.request)) })" --name "action-demo" -i "cis-demo"







 ibmcloud cis edge-functions-action-delete 

Delete an Edge Functions action of a service instance.

ibmcloud cis edge-functions-action-delete [--name ACTION_NAME] [-i, --instance INSTANCE]



 Command options 

--name
: Action name (Enterprise plan only).

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.





 Examples 

Delete Edge Functions action action-demo.

ibmcloud cis edge-functions-action-delete --name "action-demo" -i "cis-demo"







 ibmcloud cis edge-functions-triggers 

List all Edge Functions triggers for a given domain of a service instance.

ibmcloud cis edge-functions-triggers DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: The domain and path that Access will block. Required.

--session-duration value
: Defines the amount of time that the tokens issued for this application are valid. Valid values: 30m, 6h, 12h, 24h, 168h, 730h.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Update access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-app-update 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 --name exampleUpdate --domain example.com --session-duration 24h -i cis-demo







 ibmcloud cis access-app-delete 

Delete an access application (Enterprise plan only).

ibmcloud cis access-app-delete DNS_DOMAIN_ID ACCESS_APPLICATION_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.





 Examples 

Delete access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-app-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo









 Access certificate 



 ibmcloud cis access-certificate-create 

Create an access certificate for a given DNS domain (Enterprise plan only).
Show details of Edge Functions trigger 9a7806061c88ada191ed06f989cc3dac.

ibmcloud cis edge-functions-trigger 31984fea73a15b45779fa0df4ef62f9b 9a7806061c88ada191ed06f989cc3dac -i "cis-demo"







 ibmcloud cis edge-functions-trigger-create 

Create an Edge Functions trigger for a given domain of a service instance.

ibmcloud cis edge-functions-trigger-create DNS_DOMAIN_ID PATTERN_URL [--name ACTION_NAME] [--disable] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

PATTERN_URL
: The request URL which triggers the action. Required.

name
: Action name to which the created trigger is attached. (Enterprise plan only.)

disable
: Disable an Edge Functions trigger.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Create an Edge Functions trigger for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis edge-functions-trigger 31984fea73a15b45779fa0df4ef62f9b "example.net/" --name "demo-action" -i "cis-demo"







 ibmcloud cis edge-functions-trigger-update 

Update an Edge Functions trigger for a given domain of a service instance.

ibmcloud cis edge-functions-trigger-update DNS_DOMAIN_ID TRIGGER_ID PATTERN_URL [--name ACTION_NAME] [--disable] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
ibmcloud cis edge-functions-trigger 31984fea73a15b45779fa0df4ef62f9b "example.net/" --name "demo-action" -i "cis-demo"







 ibmcloud cis edge-functions-trigger-update 

Update an Edge Functions trigger for a given domain of a service instance.

ibmcloud cis edge-functions-trigger-update DNS_DOMAIN_ID TRIGGER_ID PATTERN_URL [--name ACTION_NAME] [--disable] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

TRIGGER_ID
: The ID of the trigger. Required.

PATTERN_URL
: The request URL which triggers the action. Required.

name
: Action name which the created trigger is attached to. (Enterprise plan only.)

disable
: Disable an Edge Functions trigger.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Update Edge Functions trigger 9a7806061c88ada191ed06f989cc3dac.

ibmcloud cis edge-functions-trigger 31984fea73a15b45779fa0df4ef62f9b 9a7806061c88ada191ed06f989cc3dac "example.net/" --name "demo-action" -i "cis-demo"







 ibmcloud cis edge-functions-trigger-delete 

Delete an Edge Functions trigger for a given domain of a service instance.

ibmcloud cis edge-functions-trigger-delete DNS_DOMAIN_ID TRIGGER_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

TRIGGER_ID
* CLI
* API







 Using service endpoints to privately connect to CIS 

To ensure that you have enhanced control and security over your data when you use IBM Cloud® Internet Services, you have the option of using private routes to IBM Cloud® service endpoints. Private routes are not accessible or reachable over the internet. By using the IBM Cloud private service endpoints feature, you can protect your data from threats from the public network and logically extend your private network.

When using the CIS private endpoint, any DNS records or global load balancers can be reached on the public network.



 Before you begin 

To get started, enable [virtual routing and forwarding (VRF) and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) for your infrastructure account. After you enable VRF for your account, you can connect to CIS by using a private IP that is accessible only through the IBM Cloud private network.

To learn more about private connections on IBM Cloud, see [Service endpoints for private connections](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview).





 Setting up service endpoints for CIS 

To connect to CIS by using a private network connection, you must use the CIS API or the [CIS CLI plug-in](https://cloud.ibm.com/docs/cis-cli-plugin?topic=cis-cli-plugin-cis-cliprivate-endpoint-support). This capability is not available from the CIS UI.





 Targeting private endpoints 

Before you target a private endpoint for CIS:



1. Ensure that your IBM Cloud infrastructure account is enabled for [virtual routing and forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf).

When you enable VRF, a separate routing table is created for your account, and connections to and from your account's resources are routed separately on the IBM Cloud network.