I have an example of a secured URL that we have within our application. We are getting invalid results when using Chrome as our browser. Is there something we can do within the code to stop this from happening so we have a valid URL?

URL within WebFOCUS: href="/https.secure05/RetirementServiceCenter/memberview?page_name=investmentsmanage" id="othInvestUrl" style="float:right;">Change your investment allocation
NOTE: I removed the "< a" and "< / a>" from above so you can see the actual code from WebFOCUS.

The user sees a link on the page "Change your investment allocation". If I click on the link from IE, the link works and looks like this: "https://secure.principal.com/https.secure05/RetirementServiceCenter/memberview?page_name=investmentsmanage"
If I click on that same link from Chrome, we get this link: "http://rp3.secure.principal.com/https.secure05/RetirementServiceCenter/memberview?page_name=investmentsmanage"

What causes Chrome to insert http://rp3 instead of https:// like IE? Is there something we can do in WebFOCUS to override what Chrome is doing?

Thanks!

This message has been edited. Last edited by: Stacie Stone,

This may be a question to send to TechSupport.

Is the URL a result of a drill down or is it coded into the page as shown?
In the first case, you might want to try to use the FOCEXURL setting, providing the complete correct base URL.
In the second case, you might want to code the complete address, like with the base http address included.

https://chrome.google.com/webs...akgnjflfglf?hl=en-GB


Try this in Chrome

It has been a while since I've posted an update to this issue. Still working on a resolution.

Worked with my Corp IT folks. They tell me I am invoking the base href on my page. As soon as I do that, Chrome adds the "rp3" to the front of my URLs. I want to use relative URLs in my code so I can distinguish a couple things for my user (am I in a test or production environment, did I sign in as a participant or a client, etc.). Relative URLs allow me the flexibility to create my URL based on that. One solution I was given was to switch to Absolute URLs. I've tested that solution and it will work for us but we lose the flexibility we had with relative URLs so we are still searching for what is causing us to invoke the base href.

http://www.w3schools.com/tags/att_base_href.asp

So, we are still digging into the code to see if we can locate the logic that causes Chrome to invoke the base href. Trying to find that magic "word" to search on that we might find in the code that we can fix.

Maybe this article will help:

Specifying a base URL

Thanks to the tip from CoolGuy, I was able to specify a base URL which eliminated our rp3 problem.

We are still pursuing a couple of solutions to identify environment (so I can set a different base URL based on where I'm logged in) but I am going to close this question out.

Thanks for the help! It is much appreciated.