The 6.1 version of LiteSpeed Enterprise, released on September 1, 2023, already supports the PROXY protocol.
Please also add PROXY protocol support to the open litespeed.
Our front-end uses nginx tcp stream to proxy back-end openlitespeed.
openlitespeed needs to use PROXY protocol support to get the real IP of the visitor.
"Use Client IP in Header" is impossible to obtain the real IP of visitors in the nginx TCP stream environment.
When configuring reverse proxy with nginx, the option "Use Client IP in Header" usually works fine.
However, when using nginx to proxy tcp stream, this option may not work properly.
When accessing the website, a "400 Bad Request" error is returned. This is because OpenLiteSpeed does not support the PROXY protocol. If it did support the PROXY protocol, then the error would not occur. For example, Apache or Nginx support the PROXY protocol, which would enable obtaining the visitor's real IP when using tcp stream as a proxy.
Please also add PROXY protocol support to the open litespeed.
Our front-end uses nginx tcp stream to proxy back-end openlitespeed.
openlitespeed needs to use PROXY protocol support to get the real IP of the visitor.
"Use Client IP in Header" is impossible to obtain the real IP of visitors in the nginx TCP stream environment.
When configuring reverse proxy with nginx, the option "Use Client IP in Header" usually works fine.
Code:
server {
listen 80;
server_name _;
location / {
proxy_pass http://1.1.1.1;
include proxy_params;
}
}
Code:
stream {
include proxy_streams.conf;
server {
listen 80;
proxy_protocol on;
proxy_pass 1.1.1.1:80;
}
}