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

   ### Current Behavior
   
   
   Bug : Apisix converts reponse  content types to plain/text
   
   Testing with local apisix & test api server env  (apisix on 9080 port , test 
api server with 8000 port )
   
   - Json response if request sended  directly to test api server 
   <img width="580" alt="image" 
src="https://user-images.githubusercontent.com/26168539/203670033-dde8de39-8bc6-4019-9a4b-2f263f4146c5.png";>
   
   - Converted to plain/text if request sended via apisix upstream 
   
![image](https://user-images.githubusercontent.com/26168539/203670700-fb211f5b-b867-4763-8552-6ec8ce73194d.png)
   
   Cause many type of api servers handled by apisix, some of them don't handle 
http response with json automatically,
   
   I expecting apisix not to convert response types to text/plain.
   
   Any approach or opinion will be appreciated to fix this problems 
   
   
   
   ### Expected Behavior
   
   Content type must be consist after handled by apisix upstream.
   
   
   
   
   
   ### Error Logs
   
   This seems to logical problem with apisix core, so no error logs included
   
   ### Steps to Reproduce
   
   1. send request to upstream via apisix server with Content-types: 
application/json header 
   
   2. check content types converted to plain/text
   
![image](https://user-images.githubusercontent.com/26168539/203670794-c25b4661-40ec-4b45-ba38-a17b2b48d6e0.png)
   
   
   ### Environment
   
   - APISIX version (run `apisix version`): 2.99
   - Operating system (run `uname -a`): RHEL 8
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): 1.21.4
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`): 3.5.4
   - APISIX Dashboard version, if relevant: 2.13.0
   - Plugin runner version, for issues related to plugin runners: java 17
   - LuaRocks version, for installation issues (run `luarocks --version`):  
5.4.4
   


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