I have a site where there is an existing ASMX handler service that I need to ensure still works. The path is as shown below.
~/system/services/existinghandler.asmx/EndpointName (domain removed so the forums doesn't parse the URL path)
~/system/services/existinghandler.asmx/EndpointName
As you can see, there is an existing path that I need to try and maintain, system/services.
system/services
Why is DNN intercepting this request and how would you go about forcing DNN to ignore the URL so the handler can process the request?
Did you try adding it to the "ignore URL regex"?
Thanks, John! I totally forgot about that setting!
Here's my updated code, just in case anyone else runs into this.
Original (ships with DNN):
(?<!linkclick\.aspx.+)(?:(?<!\?.+)(\.pdf$|\.gif$|\.png($|\?)|\.css($|\?)|\.js($|\?)|\.jpg$|\.axd($|\?)|\.swf$|\.flv$|\.ico$|\.xml($|\?)|\.txt$))
Updated:
(?<!linkclick\.aspx.+)(?:(?<!\?.+)(\.pdf$|\.gif$|\.png($|\?)|\.css($|\?)|\.js($|\?)|\.jpg$|\.axd($|\?)|\.swf$|\.flv$|\.ico$|\.xml($|\?)|\.txt$)|\/system\/services\/[^\/]+\.asmx(\/[^\/?]*|$))
Posted By johnhenley on 4/23/2024 10:21 AM Did it work?
Yes, it did. Thanks, John! 😎
This is exactly why I always recommend reading all the possible forum threads! you learn so much with just a few minutes of reading! Thank you John for pointing suh an important DNN feature.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.