hi andre sorry for this late reply. Your analysis is not correct. I am not trying to bypass a corporate proxy . I work independently and I have no restriction to my web access either at work or at home. In fact I had the opposite problem to solve during my vacations: trying to access my server from an hotel with a web based SSH gateway but this is another story. During my search, I found the following article and I tried to improve my understanding of apache by reproducing what is described in it. (http://www.math.polytechnique.fr/spip.php?rubrique78) Apparently the laboratory subscribed to on-line periodicals which use IP address to grant access to their customers. To provide remote access to their employees, the laboratory uses SSH + proxy : the laboratory IP address is provided to the periodical's server. I am not sure however that the laboratory was using apache for that and I did not succeed to do it myself. I obtained the same result by setting up a SOCKS proxy as described in the following article http://embraceubuntu.com/2006/12/08/ssh-tunnel-socks-proxy-forwarding-secure-browsing/ It has nothing to do with apache but it is quite useful to secure browsing from a public hotspot. thanks etienne 2009/8/26 André Warnier <aw@xxxxxxxxxx>: > Etienne, > > I am not quite sure that anyone here really understand what you are trying > to do, nor if your usage of the words "proxy" and "hosting" really matches > the usual technical meanings of these words. > > I have a suspicion that your situation might be as follows : > > - you are working on a workstation located in some organisation's internal > network > - this workstation does not have direct access to Internet HTTP servers. In > order to access an external HTTP server, you have to go through a corporate > firewall/proxy. > - that firewall/proxy does not allow you to connect to all the websites you > want to connect to, or it records the connections, which you do not like. > - so you are trying to figure out, using putty's port forwarding, if you can > somehow bypass the corporation's HTTP proxy, by using another port than 80 > to get out, and still access the external HTTP server on it's port 80. > > If the above matches your situation, I feel that I must point out to you > that > - there may be very good reasons why such a scheme is in place. Protecting > the organisation against break-ins by viruses and other nasties may be one > of them. > - by doing so, you may be violating organisation rules, and expose yourself > to bad personal consequences > > If the above is not your situation, then please provide some clearer > explanations of what you are trying to achieve, and someone might be able to > help you. > Although in principle, I don't think it has much to do with Apache. > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|