Sándor,
When you use standard junctions, there is a difference between what the browser requests and what the backend server receives.
Reverse Proxy receives: /<junction>/<backend path>
Backend receives /<backend path>
The backend server doesn't know about the <junction> so links it creates don't include it. In many cases, these links without /<junction> get back to the browser and so it makes requests back to the Reverse Proxy without them. This is probably what you are seeing.
If your menu links still work, even though the URL doesn't include the junction, then probably you don't need to worry about it. There are a number of ways that the Reverse Proxy can figure out which junction a request should be sent to even when it is missing from the request path:
- Junction cookie
- Junction Mapping Table
- Referrer header
If sounds like you're using the Junction cookie in your environment.
An alternative to these approaches above is to use "Transparent-Path" junctions. These can work when the first part of the URL path uniquely identifies the backend server. For example, if all URLs on the backend server start with /myApp/. In this case, you would make the junction name /myApp and enable transparent path junctions. Now you don't have an added junction name on the URL... the browser requests /myApp/<remaining path> and the backend receives /myApp/<remaining path>. No inconsistency any more.
If you menu links are NOT working, then you need to figure out what URL is being requested when you click the menu item. Maybe use browser trace tool to figure this out. Once you understand what is broken, hopefully a resolution can be found.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: Mon April 26, 2021 01:50 PM
From: Sándor Lakner
Subject: Junction name disapear from URL
Dear All,
We have a junctioned connection like https://websealurl/junction/path... Application uses javascripts to change the menu points inside the application.
For this, we had to enable junction cookie block support, otherwise the menu bar does not work properly.
After enabling the junction cookie block support, the junction name disappear from the URL, if we change thew menu points.
Example: https://websealurl/subpath/....
Do you have any idea why we do not see the junction name in the URL?
Thank you in advance!
Best regards,
Sándor
------------------------------
Sándor Lakner
------------------------------