Configuring Deeplink to Work with IIS Virtual Path

I have a site set up as in IIS. Additionally, I have several apps in this site, and the particular app is - the virtual path being the '/123'. I am attempting some Forgot Username/Password links from the login page as I have done without issue in the past. The only difference now is that this app is using a virtual path. My link is set to /123/link/ForgotPassword. When clicked it navigates to, but I'm getting a 404 error. I've checked my DeepLink config: Name is set to 'ForgotPassword' Microflow is selected Allow guests is enabled (also enabled in app settings) Correct alt home pg is set (index3.html) Does anyone have any ideas about what the issue might be and/or how to fix? Thanks Edit: FusionRewriter config RewriteEngine On RewriteCond %{QUERY_STRING} ^(.+)$ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond $1 !^ui RewriteCond $1 !^forms RewriteCond $1 !^mxclientsystem RewriteCond $1 !^widgets RewriteRule ^/[^/]+/([^/]+) http://localhost:8082/$1?%1 [P,L,R] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond $1 !^ui RewriteCond $1 !^forms RewriteCond $1 !^mxclientsystem RewriteCond $1 !^widgets RewriteRule ^/[^/]+/([^/]+) http://localhost:8082/$1 [P,R]
1 answers

Jason, how did you setup the rewriter in IIS. If you get a 404 error than it has to be an issue in the rewriter configuration.

Our documentation on: explains how to setup the url rewriting using the fusion rewriting library.

An important thing to consider here, is how you remove the /123/ from the original url. Because you don't want to include that part when redirecting to Mendix.

You can easily confirm and see what the exact issue is, either IIS forwards the url including the /123/ to mendix. In that case you will see the 404 message also in the Mendix log file.

Or there is no mention of the 404 in the Mendix log file, that means that IIS does not forward the deeplink url at all.

Either way you will have to take a look at the url rewriting configuration.