Hi,
Is it possible to make TCP socket and bluebox https tunnel with server on different sub domains? Actually we want to hide our original ports (9933,8080) so wanted to connect to server via two subdomains , one for tcp and bluebox each, which proxies onto server over original ports . Is it achievable ?
Regards,
TCP socket and bluebox https tunnel on different subdomains
Re: TCP socket and bluebox https tunnel on different subdomains
Sorry, I don't think I follow.
Generally speaking it's not possible because technically the server is running on the same machine, so you can only point one domain to it.
Also I am not sure why you want to "hide" the port values. The server is exposed to the outside to be able to receive connections, so what is the point of hiding it?
Thanks
Generally speaking it's not possible because technically the server is running on the same machine, so you can only point one domain to it.
Also I am not sure why you want to "hide" the port values. The server is exposed to the outside to be able to receive connections, so what is the point of hiding it?
Thanks
Re: TCP socket and bluebox https tunnel on different subdomains
Hi Lapo,
Here, the idea was to hide the original tcp port using a proxy (i.e DDOS prevention service) in our case .
Regards,
Here, the idea was to hide the original tcp port using a proxy (i.e DDOS prevention service) in our case .
Regards,
Re: TCP socket and bluebox https tunnel on different subdomains
If the proxy is able to work with the SFS2X binary protocol it can be done. A SOCKS proxy should work, in theory. (we have never tried it)
For HTTP/BlueBox a normal HTTP proxy should do the trick.
Cheers
For HTTP/BlueBox a normal HTTP proxy should do the trick.
Cheers
Who is online
Users browsing this forum: No registered users and 82 guests