I am trying to resolve a client's problem and I had an (bad?) idea...
The problem :
Client has two web servers running behind his wan router. (physical servers in his building)
Each server hosts a different web service and merging down the two servers is not an option.
The router forwards requests on port 80 to server A (and that can't change) and requests on port 90 to server B.
([[EDIT]] : Right now server B is interrogated directly from the web browser via the client's IP and port 90... This is wrooooong...)
I need to interrogate server B via a PHP (proxy) script from a 1and1 mutualized server.
The hosting company (1and1) has a firewall that prevent developers from sending requests on other ports than 21, 22 and 80.
The idea :
Changing my client's router's port forwarding rules so that server B is accessible via port 22, and sending requests via php on port 22.
The question :
Is it a terrible practice to use port 22 for http requests?
Is there a simple way to test my PHP proxy script in the first place by sending an http request to a (any) server's port 22?