You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apisix is deployed through a Helm chart in AWS EKS.
When I call the URL https://tasklist.camunda.example.net on port 443, a 302 redirect occurs, and the port in the address bar changes to 9443. The call chain stops working because the AWS NLB listens on port 443.
A similar issue occurred with a 301 redirect, but it was resolved by adding the following parameter to config.yaml:
redirect:
https_port: 443
How can this be fixed for a 302 redirect? How to configure it so that the port is 443 and does not change?
Environment
APISIX version (run apisix version): 3.11.0
Operating system (run uname -a): Linux apisix-internal-59d79555bb-b8j4x 5.10.228-219.884.amzn2.x86_64
OpenResty / Nginx version (run openresty -V or nginx -V): openresty/1.25.3.2
The text was updated successfully, but these errors were encountered:
Description
Apisix is deployed through a Helm chart in AWS EKS.
When I call the URL https://tasklist.camunda.example.net on port 443, a 302 redirect occurs, and the port in the address bar changes to 9443. The call chain stops working because the AWS NLB listens on port 443.
A similar issue occurred with a 301 redirect, but it was resolved by adding the following parameter to config.yaml:
How can this be fixed for a 302 redirect? How to configure it so that the port is 443 and does not change?
Environment
apisix version
): 3.11.0uname -a
): Linux apisix-internal-59d79555bb-b8j4x 5.10.228-219.884.amzn2.x86_64openresty -V
ornginx -V
): openresty/1.25.3.2The text was updated successfully, but these errors were encountered: