We're not hosting only our vpn on it but also a website published throught pulse secure with autentication
the same url is used internally also but used as a http website. Now certain browsers especially Internet Explorer is trying to resolve the page towards a https website (probably because of this setting) internally but that one is running http with SSO enabled.
so people that are surfing towards the website externally and are coming in the office the next day have troubles viewing this website "page cannot be displayed / found"
so with the host file its possible to edit u mean?
I may have misread your initial inquiry (apologies); are you referring to the HSTS header detail? If yes, there is nothing that can be adjusted for that. I do not believe the behavior can be changed without clearing cache & cookies due to how HSTS works; does that that even allow it to connect?
Yes indeed the hsts header max -age. I can find it for example on apache webserver. But cant find if its possible to change this setting somewhere on pulse secure. The behaviour of browser is because of the hsts header max age, which implies that the qoecific website is cached to redirect/forces to try opening the website in https
Thank you for confirming on what you are looking to do. That file is not available for editing on the PCS nor is there a config toggle to adjust that value. If that is something you need, as it sounds like you do, I would recommend reaching out to your account team for an enhancement request to allow editing or admin control of that data