Forum Discussion
NimbostratusF5 URL for the external world
Hi !
We've published the Portal URL for external users as below:
HTTPS Request from the external world-->F5-->HTTP request to SAP Web Wispatcher-->HTTP Request to SAP.
The main Portal HTTPS link works Ok...but the minute we login, it converts to HTTP.
The trace shows port 443 over the F5 getting converted to port 80. We want this URL to stay put on port 443 (HTTPS Port) & not use port 80 at all.
Kindly help advise how we could go about this.
Thanks a lot ! saba.
5 Replies
Seth_CooperEmployee
Hi Saba,
This issue could be because the backend app is redirecting to HTTP or a configuration item/issue on the F5. Your best bet on this one is to open a support case with F5 and provide a HTTPWatch, packet capture and qkview of the issue so that Support can troubleshoot your issue.
Seth
Sunshine007_217Hello Seth,
Thanks a lot ! It converts to HTTP even if I access local Portal iViews :(
If you can please advise on anything that we could check on the F5, would be great :)
Thanks a lot ! saba.
- Seth_CooperSaba, Just to confirm what you are saying... when you access the application outside of the APM you get converted to HTTP also? If so you can either have the app fixed or you can write an iRule to adjust this for you. Can you please clarify the information on if it works directly to the web app? Seth
- Sunshine007_217Hello ! Sorry I wasn't clear earlier. We have our Portal system connected to backend SAP systems. So some buttons are backend iViews & some are local Portal buttons. Irrespective of what one tries to access, the minute the credentials are passed, even before the page opens up, the protocol (in the main URL) switches to HTTP in the blink of an eye :( We'll check Yann's link below too... Thanks a lot :) saba.
Yann_DesmarestCirrus
Hello,
You will need to do rewriting with irules and stream profiles for example.
here you can find some examples :
https://devcentral.f5.com/articles/ltm-stream-profile-multiple-replacements-regular-expressions
You can start rewriting http: to https: and see if this issue is solved. But at the end, you will need to be more specific in order to avoid unwanted rewriting.
