Hello Treephat,
You can't directly create a junction as you describe. There are three types of junction:
1) Standard Junction. Matches on path. Path is modified to remove junction component:
https://www.webseal.com/app/webapp/page.html ----> https://host.backend.com/webapp/page.html2) Transparent Path Junction. Matches on path. Path is not modified:
https://www.webseal.com/webapp/page.html ----> https://host.backend.com/webapp/page.html3) Virtual Host Junction. Matches on the Host header. Path is not modified.
https://host.backend.com/webapp/page.html ----> https://host.backend.com/webapp/page.htmlIn your case, you could use a Standard Junction if you don't mind the reference to webapp being in the URL accessed by customer:
https://www.webseal.com/web1/webapp/page.html ---->
https://192.168.10.10/webapp/page.htmlIf you wanted to replace /web1 with /webapp in the Reverse Proxy you could use an HTTP Transformation to do this. Transformations are done before junction processing:
https://www.ws.com/web1/page.html -> https://www.ws.com/webapp/page.html -> https://192.168.10.10/webapp/page.html
- ----Transformation---> -----Junction------>Modifying the path in this way, you would very likely have issues with Links returned from the backend application which would reference /webapp. These would arrive back at the client. They might work in some cases but things like path based cookies could have an issue. You would need to test.
Cheers... Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------