Dotnetnuke hijacks IIS Default Documents?

Asked Sep 09 '18 at 00:51

Active Sep 18 '18 at 19:14

Viewed 28 times

After upgrading an older site to Dotnetnuke 9.2, all URLs to default documents fail (non-dnn folders).

For example:

DnnSiteDomain.com/podcasts <-- Fails
DnnSiteDomain.com/podcasts/default.asp <-- Works
DnnSiteDomain.com/podcasts/default.aspx <-- Works
DnnSiteDomain.com/podcasts/default.html <-- Works

This worked fine for years, and now all of a sudden doesn't work anymore. DNN is intercepting the URL and sending it to 404 (instead of the default IIS file), is there a setting somewhere to fix this?

edited Sep 18 '18 at 19:14

asked Sep 09 '18 at 00:51

Brad Bamford

3,783
3
22
30

Brad, what'd you do, upgrade from Pre DNN 7.1? :P – Chris Hammond Sep 09 '18 at 01:45
@ChrisHammond pretty much yeah, but didn't see this coming. Any fix? – Brad Bamford Sep 11 '18 at 21:43

Dotnetnuke hijacks IIS Default Documents?

0 Answers0