topic Re: AppSec WAF cannot set proxy_read_timeout in WAF

AppSec WAF cannot set proxy_read_timeout

AS2021 — Tue, 29 Aug 2023 07:57:28 GMT

Hi everyone,

One of our client facing issue that not able to set proxy_read_timeout.

They would like to set these custom values:

proxy_read_timeout 300;

proxy_connect_timeout 300;

proxy_send_timeout 300;

Deploy will fail until remove one or both of the “Connect Timeout” parameters.

They got this in configuration:

The proxy_read_timeout parameter is not passed into it.

Anyone can help ?

Thanks

Re: AppSec WAF cannot set proxy_read_timeout

yuvalmamka — Tue, 29 Aug 2023 08:07:25 GMT

Hi,

What is the type of deployment? How did you add these configurations?
What error do you get while deploying? And what it takes to resolve it from your tries?

Re: AppSec WAF cannot set proxy_read_timeout

AS2021 — Tue, 29 Aug 2023 08:14:15 GMT

Hi

Deployment is done via gui

The Gui immediately changes it to:

The result will be this:

Deploy will fail until I remove one or both of the “Connect Timeout” parameters.

Re: AppSec WAF cannot set proxy_read_timeout

yuvalmamka — Tue, 29 Aug 2023 08:19:58 GMT

So, basically, the UI is adding another "Connect Timeout" config line?
And then you need to remove it in order for the deployment to succeed?

After you do that, everything is working as expected?

Re: AppSec WAF cannot set proxy_read_timeout

AS2021 — Tue, 29 Aug 2023 08:23:24 GMT

No changes occur when removing the timeout despite wanting to change it to 300.

Re: AppSec WAF cannot set proxy_read_timeout

yuvalmamka — Tue, 29 Aug 2023 08:26:51 GMT

Ok, you can add these configuration in another way:

Create a .txt file with these lines in it:

proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_send_timeout 300;
Mark V near the additional server block instructions and upload the .txt file.
Click Ok and Enforce the policy.

Re: AppSec WAF cannot set proxy_read_timeout

AS2021 — Fri, 01 Sep 2023 13:24:24 GMT

Hi yuvalmamka,

Solution worked for our client, thank you for your suggestion. Just a note that we had to first reset all parameters back to their original settings before we could upload the new ones, but then it worked.