SQL CLIENT page can not run query when configuring coordinator using port 80.
We found that the problem is the web ui sending query request with the wrong port.
We show the web ui in http default 80 prot, but it send query statement request with 8080 port, so the actual request url is:
http://localhost:8080/v1/statement.
When I config to use non-80 port, for example 9090, the web ui can detect the right port to send query request:
http://localhost:9090/v1/statement.
Only not working with port 80, it will fallback to use the system default value 8080.
I don't have a test on the https default 443 port, I suppose it is also not working.
SQL CLIENT page can not run query when configuring coordinator using port 80. We found that the problem is the web ui sending query request with the wrong port. We show the web ui in http default 80 prot, but it send query statement request with 8080 port, so the actual request url is:
http://localhost:8080/v1/statement
.When I config to use non-80 port, for example 9090, the web ui can detect the right port to send query request:
http://localhost:9090/v1/statement
.Only not working with port 80, it will fallback to use the system default value 8080.
I don't have a test on the https default 443 port, I suppose it is also not working.
Your Environment
Expected Behavior
When configuring the coordinator using port 80 as http service, the post url shoud use the 80 port to send http request.
Current Behavior
But currently it will fallback to use the system default value 8080.
Possible Solution
I'm not sure where the bug is, but probably in the react frontend project.
Steps to Reproduce
show catalogs
, click run button.Screenshots (if appropriate)
Context