Hello,
I have a customer working on switching from http to https with their Laserfiche web apps. For example, right now, they have URLs bookmarked at their various workstations that look like http://servername/laserfiche/ or http://servername/forms/ , as well as some workflows that go out with links to documents and folders that use this same format. This is all for their internal network - nothing that can be accessed publicly.
When they get a valid certificate to bind in IIS, I'm assuming the CN will be servername.domain.com, which I'm also assuming means that the URLs will need to be https://servername.domain.com/laserfiche/ or the browser will throw an error. Is there a good way to get this to work seamlessly without trying to update bookmarks on client PCs? Could a URL Rewrite rule be the solution here?
Thanks!
Question
Question
Web Client - Switching from http to https
asked on October 24, 2023
•
Show version history
0
0
Replies
replied on October 24, 2023
More than likely you are correct in that the certificate will be for the FQDN of the server. With DNS entries they could use a different address altogether.
You can use the URL Rewrite module in IIS to reroute traffic from http://servername/ to https://fqdnservername/ by following the instructions in this StackOverflow post.
2
0
replied on October 24, 2023
You're right that the certificate will likely be issued to "server.example.com", but it is possible to have "server" by itself as a Subject Alternative Name. That will allow browsers to use the short name without warning. I think this is a relatively common strategy for exactly this migration path.
1
0
You are not allowed to follow up in this post.