-----BEGIN PGP SIGNED MESSAGE----- Ramon Acedo <[EMAIL PROTECTED]> writes:
> I know that apache can manage vhosts and I could redirect to a intranet > host all the web traffic coming to www2.mydomain.org, the same can be > done with wu-ftp or proftp where u can have multiple domains/dubdomains > and have different ftp root directorys depending on the name the client > used to contact it, and then I could set that roots pointing to nfs > mounted directories of the internal net, but what I'd like is that all > the traffic forward would depend on the name used by the client. without help from the protocol itself, there is no way to do 1ip virtual hosting. Apache can do it because the client sends an extra header with the request (Host:) that specifies the host you want by name. So, apache can look at the data and route the request to the right virtual host. There is no equivalent suport for virtual hosting for most protocols. There absolutely is *no* way to do this genericly. ipv6 should help with this problem, maybe in another 10yrs. - -- - -rupa -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: Processed by Mailcrypt 3.5.6, an Emacs/PGP interface iQEVAwUBPGsCb3HDM4ucEopdAQGeQwf/es+/AXESB5pdypylqITTgbcWgMyP8cfI Lgf5gjyHMaxnpmzrsjd5sx93DMxuoi2D2nCwYPxmPV3Ba2oQ3N81GH3bf8LH5JVx HK48pnKp4qSMwBI49FvW4MwB3spnHZ3gc/GEOs6MXzstQ2qadQxDFlI6D5eIbvxc rLv6JXizXYR7y6QJfsxAcw/F10qzqVppUv4G7+lCotQNigYrX2ky+VTTH8YEDi2Q pLyeAD9eMKy9xsfP3PShdLcoohId6N+H37cYu7Asz//Oj95rVAutaxVCQNeQv3qx YulfLWwQ1rdCNd1f+RRysQ3Ew/ANwpe9qoGdPD1BOmx24jg3CpAxdw== =gs5T -----END PGP SIGNATURE-----
