you are dealing with some very cutting edge place when using ATS, let us split 
down
the situation into many steps to archive:
1, do the remap
map http://Ula.ve/ingeneria/ http://190.168.24.33:8080/ingeneria/
this will tell ATS to direct all access to Ula.ve/ingeneria to the hiding 
192.168.24.33:8080
and only can ATS do so, if your contents(links, images…)in the HTML also using 
Ula.ve/ingeneria/
too. this will connect to the step2.

2, understanding the linking in html
well, in HTML or other dynamic system(php, perl…), the linking will be complex. 
there will be two
types of linking:
a. absolute path, when site using /image/xxx for images etc.
b. the relative path, the site using ./image/xxx for images.
c. to make it more complex, you can choose to use the DNS name to links, to 
make absolutely uniq:
http://Ula.ve/ingeneria/image/a.jpg is such a case.

well, after ATS remap, your user will get the 
http://190.168.24.33:8080/ingeneria/index.html from
http://Ula.ve/ingeneria/index.html. anything still using 
http://190.168.24.33:8080/ for links will
not be access-able.

3, reverse map(redirections)
what is the reverse map? when your http://190.168.24.33:8080/ want to do 
301|302 redirections,
they don’t know what is your front DNS name, in your case, Ula.ve. the reverse 
map will help
ATS rewrite the Location: header into the http://Ula.ve/ingeneria/xxxxxx, thus 
the redirected URL
will still where we want it to be. so the reverse map should looks like:
reverse_map http://190.168.24.33:8080/ingeneria/ http://Ula.ve/ingeneria/

4, conclusion:
then you will know what remap and reverse map do for you, and only do that for 
you. so bad.

and from here you can:
1, find out the linking issue for the internal site, use relative will works 
perfect in your case.

2, find some tools to rewrite the links in html to archive this.
and the good point is ATS can do what you want to with the powerful plugin 
system.

hope this will help you out.


- Yongming Zhao 赵永明

> 在 2016年6月15日,上午2:58,Paul Zambrano <[email protected]> 写道:
> 
> Dear, thank you. I'll explain in a general way, I'm testing as reverse
> proxy from my computer, I am using ATS for the excellent and good
> references from the Internet. The test consists of the following, we
> have several sites in several (non-commercial only educational) web
> servers. But we have only one official DNS, in this case (ULA.ve)
> everything should be transparent and link as follows:
> Client request
> Ula.ve/ingeneria
> translated Request
> 190.168.24.33:8080/ingeneria
> 
> another example
> ula.ve/arquitectura
> 190.168.24.32:8080
> 
> (This is hypothetical) what we want is to act as reverse proxy.
> 
> The first test that I did run, hiding in all links performing the url of
> the server hosting, always showed links and returned by the reverse
> proxy addresses ula.ve/ingeneria/estudiante know ... but I had to
> install another ATS machine and then did not return to work.
> if I disable proxy.config.url_remap.pristine_host_hdr CONFIG INT 0
> excellently page load all images and all styles but only makes a
> redirect and therefore does not hide the addresses of hosting server
> 
> El 14/06/16 a las 10:53, Alan Carroll escribió:
>> 
>> 
>> I haven't done that much with remap but I played with it a bit this morning 
>> and I ended up unclear on what the actual goal is.
>> 
>> My recommendation would be to add an additional identity rule for ula.ve
>> 
>> map http://www.ula.ve/ http://www.ula.ve
>> map http://190.168.24.33:8080/ula/ http://www.ula.ve/
>> reverse_map http://www.ula.ve/ http://190.168.24.33:8080/ula/
>> 
>> 
>> The reverse_map rule, as far as I can tell, applies on to redirects and not 
>> to any HTML content in a returned web page. Therefore such things as style 
>> sheet links will not be modified and if they contain absolute URLs (which, 
>> frankly, is a bad idea for exactly this kind of reason) then such requests 
>> will hit the ula.ve address. As this is a reverse proxy, the question how a 
>> user agent gets the raw IP address and port 8080 for the initial request. 
>> Normally the DNS would be set so that ula.ve resolved to the ATS instance 
>> address and it would then either remap to raw IP addresses of the origin 
>> server or the origin server would have a different but non-public name that 
>> could be resolved by ATS.
>> 
>> 
>> On Tuesday, June 14, 2016 8:28 AM, Paul Zambrano <[email protected]> wrote:
>> 
>> 
>> 
>> good morning , Dear friend , excuse me yesterday sin electrical energy.
>> My country is suffering ... but hey we do what we can. The link returns
>> is the original host server.
>> 
>> http://www.ula.ve/estudiar-en-la-ula-venezuela
>> 
> 
> -- 
> T.S.U Paul Zambrano
> Universidad de Los Andes
> Direccion de Telecomunicaciones y Servicios
> Centro Nacional de Calculo Cientifico
> Tlf: 0274 - 2524192
> Cel: 0414 - 7294597 / 0426 - 1534959

Reply via email to