You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Does Web Client not support using alternative web ports?

Web Client
Updated January 6, 2021
posted on December 22, 2020

There is a request to use an alternate port binding, instead of the default 443. This has never been a problem in the past but this is the latest release of Laserfiche.

It still works fine with Forms by updating the Forms URL in the config to include the port in the URL

https://domain:port/Forms

However in web client, even if you specify https://domain:port/laserfiche in the Laserfiche Web Client URL and https://domain:port/LFDSSTS/ in the Directory Server configuration it still removes the :port in the browser when you visit the website, trying to default back to the 443 port

Forms works fine, with STS and everything. Web Client, first thing it does when you visit the site is removes your port specification from the URL and then complain that https://domain/laserfiche does not exist.

0 0
replied on January 6, 2021 • Show version history

It works for me. Did you update the public url for web client in the configuration page? That's what it uses to build the url to redirect back from LFDS.

0 0
replied on December 22, 2020

What's the use case behind changing the standard HTTPS port?

I've never heard of changing standard points being anything beyond questionable security by obscurity at best, and this one breaks default browser behavior for legitimate end users in the process.

0 0
replied on December 23, 2020

Usually it is because they run out of external IP addresses to route 443 traffic. I guess I will ask if they can go back to 443 in this case, this is the only product that isn't allowing it.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...