Skip to content

Commit f5ea87e

Browse files
committed
docs(ic-http-certification): improve example docs
1 parent bfcebc4 commit f5ea87e

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

examples/http-certification/assets/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -347,13 +347,13 @@ Then, deploy the canister:
347347
dfx deploy http_certification_assets_backend
348348
```
349349

350-
You can now access the canister's assets by navigating to the canister's URL in a web browser. The URL can also be found using the following command, making sure to replace `backend` with the name of the canister:
350+
You can now access the canister's assets by navigating to the canister's URL in a web browser. The URL can also be found using the following command:
351351

352352
```shell
353353
echo "http://$(dfx canister id http_certification_assets_backend).localhost:$(dfx info webserver-port)"
354354
```
355355

356-
Alternatively, to make a request with cURL, again making sure to replace `backend` with the name of the canister:
356+
Alternatively, to make a request with `curl`:
357357

358358
```shell
359359
curl "http://$(dfx canister id http_certification_assets_backend).localhost:$(dfx info webserver-port)" --resolve "$(dfx canister id http_certification_assets_backend).localhost:$(dfx info webserver-port):127.0.0.1"

examples/http-certification/custom-assets/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -360,7 +360,7 @@ fn certify_index_asset() {
360360
}
361361
```
362362

363-
It's also possible to skip certification for certain routes. This can be useful for scenarios where it's difficult to predict what the response will look like for a certain route and the content is not very security sensitive. This can be done as follows:
363+
It's also possible to skip certification for certain routes. This can be useful for scenarios where it's difficult to predict what the response will look like for a certain route and the content is not very security sensitive. This can be done for example with metrics served on the `/metrics` route as follows:
364364

365365
```rust
366366
const METRICS_REQ_PATH: &str = "/metrics";
@@ -562,13 +562,13 @@ Then, deploy the canister:
562562
dfx deploy http_certification_custom_assets_backend
563563
```
564564

565-
You can now access the canister's assets by navigating to the canister's URL in a web browser. The URL can also be found using the following command, making sure to replace `backend` with the name of the canister:
565+
You can now access the canister's assets by navigating to the canister's URL in a web browser. The URL can also be found using the following command:
566566

567567
```shell
568568
echo "http://$(dfx canister id http_certification_custom_assets_backend).localhost:$(dfx info webserver-port)"
569569
```
570570

571-
Alternatively, to make a request with cURL, again making sure to replace `backend` with the name of the canister:
571+
Alternatively, to make a request with `curl`:
572572

573573
```shell
574574
curl "http://$(dfx canister id http_certification_custom_assets_backend).localhost:$(dfx info webserver-port)" --resolve "$(dfx canister id http_certification_custom_assets_backend).localhost:$(dfx info webserver-port):127.0.0.1"

0 commit comments

Comments
 (0)