Forum Discussion
supportrsd_1762
Nimbostratus
NimbostratusConfused of link the external links in a webapplication
Hello, im at a client that has published a webapplication. This webapplication has three links (that goes to different webshop with logins Im a bit confused about the behavior. First none of the links worked, the customer had this error.
"Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please."
Then they links to a bypass list, but still got errors. Before we did not have a serverssl profle on the virtualprofile for the protal, but we when they added the serverssl profile Serverssl-insucure-compatible. It worked better. There is one link that does the authentication in the link (like this), i know its no good.
https://www.webshop.com/cgi-bin/sfti/webshop_login.cgi?USERNAME=orange&PASSWORD=apple&HOOK_URL=[er
The apm dont seem to send the link. But still. I cant really understand why it did not work when i had no serverssl profle? And it started to work when i added it? If i have the links in bypass they should just open as normal in the webrowser.
supportrsd_1762I still got problem with this link
https://www.webshop.com/cgi-bin/sfti/webshop_login.cgi?USERNAME=orange&PASSWORD=apple&HOOK_URL=[er
The f5 seems to bypass to link, but it wont send this ?USERNAME=orange&PASSWORD=apple&HOOK_URL=[er I land at https://www.webshop.com/cgi-bin/sfti/webshop_login.cgi
- supportrsd_1762
I will check this out at the end of the week when im at that client.
- supportrsd_1762
Well tbh the client/customer did some playing around with this without me so i dont really now about that detail :)
- Eric_St__John
Employee
If the changes didn't take effect, I would suspect one of the following: 1. Didn't "Apply Access Policy" 2. Didn't Logout/Login - I would clear browser cache, and close/re-open for good measure 3. Syntax is incorrect in the "Bypass List" Eric
- Eric_St__John
Did you logout, clear browser cache, then logon again?
The serverssl profile instructs the BIG-IP to open the server side connection with HTTPS, rather than HTTP. That would explain why it worked correctly after adding the serverssl profile.
Eric
