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: content/nginxaas-azure/quickstart/hosting-static-content-blob-storage.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ F5 NGINXaaS for Azure (NGINXaaS) can serve static content stored in Azure Blob S
20
20
21
21
### Step 1: Upload static files to the $web container
22
22
23
-
Place your static files in the `$web` container in your storage account. This is the standard container used for static website hosting in Azure.
23
+
Upload your static files to the `$web` container in your storage account. This is the standard container used for static website hosting in Azure.
24
24
25
25
### Step 2: Configure network access
26
26
@@ -40,7 +40,7 @@ Place your static files in the `$web` container in your storage account. This is
40
40
4. Optionally, set an **Error document path** for 404 errors.
41
41
5. Click **Save**.
42
42
43
-
Note the **Primary endpoint** URL that appears after enabling static website hosting. You'll need this for your NGINX configuration.
43
+
Note the **Primary endpoint** URL that appears after enabling static website hosting. You'll use this URL in your NGINX configuration.
44
44
45
45
## Configure NGINXaaS
46
46
@@ -99,10 +99,10 @@ Upload your NGINX configuration to your NGINXaaS deployment following the instru
99
99
100
100
## Verify traffic routing
101
101
102
-
You can verify that requests are properly routed through your NGINXaaS deployment by checking the Azure Storage logs:
102
+
You can verify that requests are properly routed through your NGINXaaS deployment by examining the Azure Storage logs:
103
103
104
104
1. Enable logging for your storage account if not already enabled.
105
-
2. In the storage logs, you should see requests coming from the private IP address of your NGINXaaS deployment, not from public Internet addresses.
105
+
2. In the storage logs, you should see requests originating from the private IP address of your NGINXaaS deployment, not from public Internet addresses.
0 commit comments