return200 commented on issue #4942:
URL: https://github.com/apache/apisix/issues/4942#issuecomment-997832395


   > ### Issue description
   > If the upstream service through the APISIX proxy returns 302 redirect, the 
client redirected the port to the 9080 port of apisix,
   > 
   > For example, client access [http://a.com:80/,](http://a.com:80/%EF%BC%8C)
   > 
   > Normally, it would be redirected to the http://a.com:80/login
   > 
   > But it’s actually redirected to the http://a.com:9080/login
   > 
   > ### Environment
   > * apisix version: 2.7.0(helm chart installed,and chart version is 
apisix-0.3,6)
   > * apisixroute:
   > 
   > apiVersion: apisix.apache.org/v2beta1 kind: ApisixRoute metadata: name: 
jenkins namespace: jenkins spec: http:
   > 
   > * name: jenkins
   >   match:
   >   hosts:
   >   
   >   * eks-jenkins-test.invik.com
   >     paths:
   >   * /*
   >     backend:
   >     serviceName: jenkins2
   >     servicePort: 8080
   >     plugins:
   >   * name: ip-restriction
   >     enable: true
   >     config:
   >     whitelist:
   >     
   >     * 39.106.1.281/32
   >     * 192.168.0.0/16
   > 
   > Service:
   > 
   > apiVersion: v1 kind: Service metadata: name: jenkins2 namespace: jenkins 
spec: ports:
   > 
   > * name: web
   >   port: 8080
   >   protocol: TCP
   >   targetPort: web
   > * name: agent
   >   port: 50000
   >   protocol: TCP
   >   targetPort: agent
   >   selector:
   >   app: jenkins2
   >   sessionAffinity: None
   >   type: ClusterIP
   > 
   > ### Steps to reproduce
   > 1.client access [http://a.com:80/,](http://a.com:80/%EF%BC%8C)
   > 
   > 2.Normally, upstream response 302 to the http://a.com:80/login
   > 
   > 3.But it’s actually redirected to the http://a.com:9080/login
   > 
   > ### Actual result
   > 3.But it’s actually redirected to the http://a.com:9080/login and the 
browser is waitting
   > 
   > ### Error log
   > the browser return: 无法访问此网站eks-jenkins-test.invik.com 的响应时间过长。
   > 
   > ### Expected result
   > _No response_
   
   where does your domain a.com resolve to? Add `proxy_set_header 
X-Forwarded-Port $server_port; ` if nginx; if it's a slb/alb, there should have 
a configuration to add the header `X-Forwarded-Port`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to