You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: examples/http-certification/assets/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -347,13 +347,13 @@ Then, deploy the canister:
347
347
dfx deploy http_certification_assets_backend
348
348
```
349
349
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:
351
351
352
352
```shell
353
353
echo"http://$(dfx canister id http_certification_assets_backend).localhost:$(dfx info webserver-port)"
354
354
```
355
355
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`:
357
357
358
358
```shell
359
359
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"
Copy file name to clipboardexpand all lines: examples/http-certification/custom-assets/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -360,7 +360,7 @@ fn certify_index_asset() {
360
360
}
361
361
```
362
362
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:
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:
566
566
567
567
```shell
568
568
echo"http://$(dfx canister id http_certification_custom_assets_backend).localhost:$(dfx info webserver-port)"
569
569
```
570
570
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`:
572
572
573
573
```shell
574
574
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