Invalid HTTP Configuration log when using Max Duration Timeout variable - Layer7 API Gateway

Products

• CA API Gateway

Issue/Introduction

This article describes a configuration error encountered when using the Max Duration Timeout feature in the Route via HTTP(S) assertion.

• When enabling Max Duration Timeout and using a context variable (e.g., ${gateway.io.outTimeout}) as the value, the Gateway logs an Invalid HTTP Configuration 'Max Duration Invalid ' error.
• The routing may fail or not respect the dynamic timeout value.
• Using a constant integer value (e.g., 8000) works as expected

Environment

Layer7 API Gateway 11.2.x

Cause

This is caused by a product defect (DE683708) where the Max Duration Timeout runtime handling fails to resolve context variables correctly.

Resolution

Fixed in release Gateway 11.2.1 July 2026 MSP and higher. See Download Broadcom Products and Software for steps to download this release.

Workaround: To use a context variable in the Max Duration Timeout field, force the Gateway to load the variable by referencing it in the URL field of the Route via HTTP(S) assertion:

1. Open the properties for the Route via HTTP(S) assertion.
2. In the URL field, append a dummy query parameter containing the variable: https://####:####/endpoint?load=${gateway.io.outTimeout}
3. The variable will now be correctly recognized in the Max Duration Timeout field.

Additional Information

• For further updates on this defect, please subscribe to this article.
• To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.