Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.13.2 GA
-
3
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
API CCS Sprint 44 (3Scale) 2
Description
The timeouts configured in Upstream Connection have no effect on the timeouts when Camel Policy is used (further details related to http/https in point 4 below). The expectation from application perspective is that the timeout should apply whether Camel Policy is used or not.
The following JIRA/Comments have created for clarifications related to this issue.
- Upstream in docs seems to be referring to API backend - THREESCALE-10580 has been created for clarification.
- Note regarding load balancing disabled - THREESCALE-10581 needs clarification on whether this means Upstream Connection policy does not apply when Camel Policy is used.
- Upstream Connection is configuring NGINX directives, which would take effect only when APIcast connects to upstream (API backend) . It is unspecified if this would work when Camel Policy is being used i.e. if Camel Policy is compatible with Upstream Connection or not.
- Timeouts configured in Upstream Connection do work when http is used ( http_proxy, and API backend accessed using http), but not with https (https_proxy, API backend accessed using https )
Pending clarifications to the above, marking this issue as a bug rather than an RFE.
Attachments
Issue Links
- links to
-
RHEA-2024:129854 Release of apicast-operator 0.12.1mas for RHOAM - Containers
- mentioned on