web.config urlmappings

Question

User1510859543 posted

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?

	  <urlMappings enabled="true">
		  <add url="~/misc/ReplySMS.aspx" mappedUrl="~/SMSReplyHandler.ashx" />
	  </urlMappings>

Answer 1

User753101303 posted

Hi,

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.

Answer 2

User1510859543 posted

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. Thanks.

Answer 3

User1510859543 posted

Did a test after removing the page and it still worked. Thanks.