Yes with Apache =E2=80=A6we can edit the = ..htaccess file =E2=80=A6simple and clean. Not so with Windows. IIS 7 and = above, one can use module URL Redirect. But for IIS 6 =E2=80=A6.a messy = solution. Hence the query if it can be done with WebDNA.
Using = WebDNA 8 =E2=80=A6.[thisport] works great where we can redirect after = detecting the port used. But for old Win 2003 server running WebDNA 6, = sadly this tag cannot work. Looks like the only option left would be to = use JavaScript to detect the port and redirect accordingly.
Thanks = folks =E2=80=A6.TDn
From: Paul Willis <paul.willis@me.com>
Sent: Wednesday, December 19, = 2018 19:18 PM
To: talk@webdna.us
Subject: Re: [WebDNA] Redirecting = incoming URL request to https page
Why not just do this in the web server = configuration. Not sure how it works on Windows (assume your on IIS) but = on Apache it one line in the virtual host.
Hi = folks,
Have users coming to our landing page via = unsecured link (http URL instead of https). Would like to use WebDNA to = verify that the incoming request for any WebDNA enabled pages is from a = https (secured) request =E2=80=A6.if not redirect the link to one that = is or an error page which declares the security issue.
Running = WebDNA on Windows so any pointers on how to achieve this via WebDNA is = appreciated.
By the way =E2=80=A6Merry Xmas and Happy New = Year to one and all for the coming festivities.
Cheers = TDn