Nimbostratus
NimbostratusIn developer tools when we see the response from server in client browser, it does show the frontend host as expected, but we see the server has given the backened uri as actual without including the "/x" which we removed.
Even the page that it dispays for login was not loaded properly missing images in developer tools shows that image was not able to load as it tried with direct uri from customer browser to load it eg https://abc.com/image1 rather than https://abc.com/x/image1.
MVPAbhi-netdive The reason you're having this issue is because the server does not know that the client made a request to a path with "/x/" so when it sends the literal path to the client to retrieve the images the client searches for that literal path. What is the reasoning for not allowing the client to use the real URI path and it must use the "/x/" in the path? I don't believe you will be able to get around this without editing the response from the server and adding in "/x/" to every response that it sends to the client which will complicate the configuration which will cause delays when troubleshooting.