Visual LANSA Forum

I am experimenting with the new web routing features in version 15+, but since web pages don't include the .html extension the IIS webserver returns 404 FILE NOT FOUND. When I add the .html extension to the URL the page is loaded correctly and the routing in the web application itself seems to work fine. While staying in the web application I see the URL path changing to the routes I did setup and the URL is not showing the .html extension anymore. But when I use the URL with the routing path directly a 404 FILE NOT FOUND shows up. Am I missing a setting somewhere on my IIS web server or is it something else?

As far as I know you don't need to configure something special on the IIS side. In our environment it worked without any problems after the package installation.

Do you use URL Rewrites in IIS? We had to reconfigure the rules, but nothing else.

Regards
Dominique

Thanks Dominique for the reply. We use a pretty standard IIS (version 10) install on Windows server 2016, so nothing special is done for URL Rewrites. What rules are you referring to?
Regards,
Marcel

Is it necessary to install the "URL Rewrite" extension in IIS?

No, it's not necessary but a great tool to add rules or change the URLs before redirecting to your site. But you should not have this strange behavior.

If you use .html with routing definitions, the whole Router would be something like disabled.

Did you test it with a sample page? Do you have the same behavior with that sample page?
Did you apply the epc to your IIS Server?
Is it working correctly on your dev environment?

Note: not all Routings are "public". If you add new routes you have to define if a Session is necessary or not. (Property Access(Public))

Dominique

Lansa support is looking in to it. I am still in my DEV environment where IIS is on the same machine. Lansa web plugin is not accepting any URL without .html at the end. Even the demo applications are not working.
Must be something in the configuration on the machine, but cannot find what it is.

This issue is solved by myself. Seemed to be a strayed/lost registry key causing this trouble:

[HKEY_LOCAL_MACHINE\SOFTWARE\LANSA\%5C%5CSERVERNAME%5CD$%5CLANSA] ==> this translates to \\SERVERNAME\D$\LANSA

[HKEY_LOCAL_MACHINE\SOFTWARE\LANSA\%5C%5CSERVERNAME%5CD$%5CLANSA\LANSAWEB] ==> this translates to \\SERVERNAME\D$\LANSA\LANSAWEB

After removing these entries from the registry and restarting IIS, everything worked fine. I don't have a clue where these registry entries were coming from and why this is messing up the web routing only. I have informed Lansa support.

Still having this routing problems on our external Web server (in DMZ), which only acts as a pass through to the Lansa application server on the internal network. The problematic registry entries described before, don't exist here. So we have to add the .html extensions to the URI of the Lansa web page, otherwise we get "HTTP 404 - Not Found".
Does anyone have any suggestions?