Last post Aug 13, 2020 08:24 PM by dlchase
Aug 13, 2020 07:06 PM|dlchase|LINK
We are using a urlMappings element in our web.config file and it works fine. My question is does the "url" setting have to point to an actual web page or not? For example, in the section sample below does "~/misc/ReplySMS.aspx" actually have to exist as
a physical page or will it thrown an error if it does not?
<add url="~/misc/ReplySMS.aspx" mappedUrl="~/SMSReplyHandler.ashx" />
Aug 13, 2020 07:39 PM|PatriceSc|LINK
What if you just try? Or discuss directly what you tried and doesn't work if this is the case.
I'm fairly sure this is not needed. A possible issue is to have to use
https://www.luminowebdesign.no/tech-blogg/asp-net-routing-and-web-config-setting-runallmanagedmodulesforallrequests as this option is only for url processed by ASP.NET.
Aug 13, 2020 07:44 PM|dlchase|LINK
I guess I can create a test scenario as I didn't want to mess with a production system that sends this url to the web application. Is the urlMappings the best way to handle this? Like I said it has been working fine and I need to add a 2nd urlMappings entry.
Aug 13, 2020 08:24 PM|dlchase|LINK
Did a test after removing the page and it still worked. Thanks.