i want to have both an Apache and a Game Server to be reachable on port 443 of the same IP address.
The game server connection is a normal TCP connection that is established when the client logs in and stays open until the client logs out, perhaps hours later.
At first I though about using mod_proxy in reversed mode and let the client start the communication with a request for a specific URL, but I guess that would not allow me a long time two way communications between the client and the game server.
Another idea was to use mod_proxy_connect in forward mode (with strict access rules of course) and let the client send a CONNECT request. In theory this should work.
Both mentioned attempts, however, have a huge issue: The Game Server does not see the ip-address of the client anymore. Unfortunately this is a hard requirement.
Reversing the order has the same issue: If i let the Game server listen on port 443 and forward web request to the Apache, the .php programs and the access.log would not see the real ip-address anymore. And I am a bit afraid that this approach has a negative impact on game performance. (Especially on pages which a huge number of non-cacheable images)
Operating System: Linux (Debian)
Webserver: Apache 2
Game Server and client are written in Java
Thank in advance for any ideas.
You could let Apache create a session id and store it into database and then use mod_proxy_connect. When the Game Server accepts the request from the local Apache, it should get the session id from a header and read the client’s ip address from the database.