
How to change WAF maximum upstream timeout
(Doc ID 2809466.1)
Last updated on MARCH 28, 2022
Applies to:
Oracle Cloud Infrastructure Web Application Firewall - Version N/A and later
Information in this document applies to any platform.
Symptoms
- You have a WAF policy created with ocid
- Writing the file posted by webapi to Database does not end in the default 300 seconds and result in error. You need to post a large number of records.
Changes
- Since you are not able to finish the API upload in 301 seconds, you wish to increase the Origin Keep Alive Timeout > 300
Cause
|
To view full details, sign in with your My Oracle Support account. |
| Don't have a My Oracle Support account? Click to get started! |
In this Document
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.