Hey all,

I have a custom HTML page I built using a Bootstrap and jQuery based template. Just finished it, looks and runs great when accessing it via an HTTP protocol. When we try accessing it via an HTTPS protocol inside a portal container, the drop-downs no longer work and the portal tries to tack on a bazillion style params...

I am looking for a URL build that will allow me to run the HTML page that's under a Content domain folder using HTTPS but not use the run.bip? string way of doing it to see if things would work outside of IBI's portal product or not.

Everything works fine using this URL build:

"http://serverName/ibi_apps/bip/portal/portalName"

My page no longer functions after trying to use this URL build:

   
"https://server.domain.com/ibi_apps/bip/portal/portalName"

My nav menu links that toggle the dropdowns are hijacked with some long param list and random number tacked onto the end and they no longer work.

Anyone have an idea if I could use the WFServlet call or something using HTTPS?

Any help is much appreciated!

Thanks in advance!

This message has been edited. Last edited by: CoolGuy,

If its just calling reports, etc, then WFServlet should work.

I guess its the same as a drilldown call.

Even when running the HTML with the WFServlet call the dropdowns fail to work... Blah...

Used this URL build with no luck (takes me to the page, but drop-downs are still busted):

"https://server.domain.com/ibi_apps/WFServlet.ibfs?IBFS1_action=RUNFEX&IBFS_path=/WFC/Repository/.../index.html"

It must be related to BootStrap then? Argh... Why does it work fine with an HTTP URL, but not an HTTPS URL? Weird....

Have you used the browsers Developer tools to check and see what happening.

Also is there js errors, etc.

That was my next step. Wanted to rule out IBI possibilities first, because let's face it, that's where the bugs are usually... lol

Found some discrepancies between links that blocked some things in the F12 tools error log. Will modify things and let you know what goes down when I can get to this tomorrow.

Thanks again Waz!

Basically I didn't have all links using https like I should have. My bad. Fixed it.