-
Summary
Steps To Reproduce
Additional Details & Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
kong version 2.5.0 |
Beta Was this translation helpful? Give feedback.
-
Hello @wdqzdd, It seems to me that the What is happening is that your webservice is listening to http traffic from a non-default http port (8086). The only way to communicate with a device listening on port 8086 is by sending traffic through that port. So you will always receive requests on port :8086 if that's where your service is listening. The only way to solve this is by moving your service to the default http ports - 80 for HTTP or 443 for HTTPS traffic. |
Beta Was this translation helpful? Give feedback.
Hello @wdqzdd,
It seems to me that the
preserve_host
property is unrelated with your issue. That property is used to adjust theHost
when matching via host. Your problem is not the host, but the port.What is happening is that your webservice is listening to http traffic from a non-default http port (8086). The only way to communicate with a device listening on port 8086 is by sending traffic through that port. So you will always receive requests on port :8086 if that's where your service is listening.
The only way to solve this is by moving your service to the default http ports - 80 for HTTP or 443 for HTTPS traffic.