Hello,
I have a scenario that we struggled with but I feel like I finally cracked the issue and I'd like to brag a little and field some criticism too. So please provide opinions about what you are doing in your deployments so we can figure out if we've done things the best way possible.
I have a Qlikview SBE on version 11.20.11922.0
in order to allow our mobile users to use Qlikview from ipads and other devices we have opened the environment over the internet and have implemented an SSL cert.
In addition to that we had a requirement that if the user calls the http site instead of https we want the webserver to automatically redirect the the https site.
All the threads on that topic led me to beleive that it was not possible with just the QVWS.
So at first we tried deploying Qlikview to iis. we deployed qlikview to the default web page in iis and got ssl working with few problems. then we tried to implement the redirect. THIS WAS A NIGHTMARE, the sources of information on this topic are all over the map about the best way to do this sort of thing.
- We tried various configurations of the "http redirect" feature
- Then we tried "URL rewrite"
Both of these solutions promised to be simple and "work like a charm" but our deployment was dogged by a fairly persistent "redirect loop" error. There were many iis guru's out there suggesting how to overcome redirect loops in iis but those solutions were identical to what he had already tried and failed.
We did finally get the redirect working but then we could not provide hyperlinks directly to a document, basically the redirect would cause the query string to be dropped from the url and the user would be presented with just good ol' access point instead of the document they wanted.
At this point I decided to try something radical.
I let decided that the redirect loop might be overcome if I installed IIS and QVWS. I thought that IIS could handle all the traffic on port 80 and QVWS would handle port 443
I will say that restoring iis to it's default state was not easy but once I managed to get IIS's settings cleaned up and the QVWS running with the ssl, setting up the rule for redirecting from the IIS default web site to https was easy and it worked like a charm.
To set up the QVWS with SSL I used the procedure found in the attached word document, this was put together by Bill Britt who is a regular contributer to the ssl discussion.
To set up the URL rewrite rule I used the procedure described in the attached PDF, it is a screen grab from http://www.jppinto.com/2010/03/automatically-redirect-http-requests-to-https-on-iis7-using-url-rewri... I copied it in case the blog where I found it changes or the post becomes inaccessible.
On another note, I was also able to simplify the url that the user has to call. For example the default access point URL is http://Server/qlikvew I know it is not a difficult path but if you want you can get them there with just http://ServerName.
Go into the web panel of the QVWS config page and in the Root Folders section add a folder with no name and duplicate the path found in the QLIKVIEW entry.
So the whole point of this was to get your feedback, please let me know what you think and feel free to ask any questions about how we did it.
Thanks
Chris
.png "Luminary Alumni"){kind=icon}
