bmbson opened a new issue, #12017:
URL: https://github.com/apache/apisix/issues/12017

   ### Description
   
   The problem I'm having is that routes that are requested by clients are 
redirecting to the upstream address.
   
   The behavior I want is that requests are forwarded by APISIX without the 
client getting to see or having to visit the actual upstream address.
   
   as you can see, when i request the route I get a 301.
   
   
![Image](https://github.com/user-attachments/assets/6fb8c154-3e22-4598-9e0a-c36531e14733)
   
   It then sends the user to the upstream address and gives the (correct) 
requested response. 
   
![Image](https://github.com/user-attachments/assets/1a781540-78d2-4e5d-a6cd-be9241694436)
   
   I don't want the user to ever visit the upstream, instead I'd like the user 
to get the requested data from the APISIX location. Is there a setting I need 
to turn on? Or is this how it's supposed to work?
   
   Upstream JSON:
   
   
![Image](https://github.com/user-attachments/assets/ed7807d2-85fe-4b20-8ce1-347faf4f9075)
   
   Route JSON:
   
   
![Image](https://github.com/user-attachments/assets/c3ff6b48-7f91-4f38-b4ad-87a0bb64ebca)
   
   - APISIX version (run `apisix version`): 3.11
   - Operating system (run `uname -a`): debian
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx 
version: openresty/1.25.3.2
   - APISIX Dashboard version, if relevant: 3.0.0
   
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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