Skip to content

Commit 305199c

Browse files
committed
Add more info about safety
1 parent 210dcce commit 305199c

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

content/en/security/application_security/setup/standalone/gcp-service-extensions.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,15 @@ To set up the App and API Protection Service Extension in your GCP environment,
7979
1. To send all traffic to the extension, insert `true` in the **Match condition**.
8080
2. For **Programability type**, select `Callouts`.
8181
3. Select the backend service you created in the previous step.
82-
4. Select all **Events** from the list where you want App and API Protection to run detection (Request Headers and Response Headers are **required**).
82+
4. Select only **Events** from the list where you want App and API Protection to run detection (Request Headers and Response Headers are **required**).
83+
84+
<div class="alert alert-info">
85+
<strong>Note:</strong> If you select request and response bodies events, processing time will increase as the service extension needs to transfer and analyze these bodies. Adjust your timeout settings accordingly to accommodate the additional processing time.
86+
</div>
87+
88+
<div class="alert alert-info">
89+
<strong>Note:</strong> By default, if the service extension fails or times out, the proxy will return a 500 error. To prevent this, enable the <code>fail_open</code> setting. When enabled, request or response processing continues without error even if the extension fails, ensuring your application remains available.
90+
</div>
8391

8492
</br>
8593

0 commit comments

Comments
 (0)