upstreamResponseTimeout cannot be disabled for backend

[jwgmeligmeyling]

Description

The documentation states that:

UpstreamResponseTimeout spans between the point at which the entire downstream request (i.e. end-of-stream) has been processed and when the upstream response has been completely processed. A value of 0 will disable the route’s timeout. If the timeout fires, the stream is terminated with a 504 Gateway Timeout error code.

However, when upstreamResponseTimeout: 0 is set, the default timeout of 15 seconds is still applied.

Steps to Reproduce

The following Backend configuration:

kubectl describe backend exact-nl-backend
Name:        nl-backend
Namespace:    apk
Labels:       <none>
Annotations:  <none>
API Version:  dp.wso2.com/v1alpha2
Kind:         Backend
Metadata:
  Creation Timestamp:  2025-02-25T22:19:26Z
  Generation:          3
  Owner References:
    API Version:     dp.wso2.com/v1alpha3
    Kind:            API
    Name:            exact-api
    UID:             36974d7f-928e-499b-81df-3cdb4f5d8569
  Resource Version:  716174386
  UID:               f78400a4-d046-40d1-afd0-e24c2285ca38
Spec:
  Protocol:  https
  Services:
    Host:  <>
    Port:  443
  Timeout:
    Downstream Request Idle Timeout:  0
    Upstream Response Timeout:        0
Events:                               <none>

Still has an upstream response timeout of 15 seconds applied.

Affected Component

Adapter

Version

1.2.0

Environment Details (with versions)

No response

Relevant Log Output

Related Issues

No response

Suggested Labels

No response