Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HttpHandlers under DNN 4.7.0HttpHandlers under DNN 4.7.0
Previous
 
Next
New Post
4/24/2008 1:20 PM
 

We're currently running 4.7.0 and experiencing an issue with DNN interfering with HttpHandlers.  We are trying to use the newest version of the Telerik RadChart for ASP.NET AJAX (Q1 2008 - yes, we've fully upgraded our compiled copy of DNN to .NET 3.5 including ASP.NET AJAX) and it uses a handler called "ChartImage.axd".  When it renders the image for the chart, it uses that handler as the image source.  It does not work when it is trying to access ChartImage.axd from a path like the following: /Dashboard/tabid/82/ChartImage.axd, whicih is the only path it knows to use.  If I take the URL being used as the image source and remove everything from that path except ChartImage.axd, the image renders properly.  So, is something with friendly URLs interfering with HttpHandlers?  This is really causing some great grief and we cannot upgrade to 4.8.2 yet (if it's even fixed there), so we can't test a newer version.

 
New Post
4/24/2008 2:18 PM
 

One thing that I have noticed is that all other HTTP handlers (like ASP.NET AJAX ones), use the absolute path to reference the handler.  In the case of this chart control, the image source assumes a relative path (in the HTML source output to the browser, the src attribute only references ChartImage.axd with no path), which means it gets all of the additional stuff DNN adds to it.  It seems that this is a bug in the chart control, but is there any way to temporarily fix this?  Shouldn't handlers at any path be usable since the handler captures the file reference and not the path?  Shouldn't handlers be ignored by DNN in general?

 
New Post
4/24/2008 2:54 PM
 

You may just need to exclude "ChartImage" from compression, assuming you are not already excluding .axd, and assuming you are using compression.


DotNetNuke Modules from Snapsis.com
 
New Post
4/24/2008 3:57 PM
 

You might try the following.

The existing path for the handler is

path="ChartImage.axd"

Try changing this to

path="*ChartImage.axd"

See if that has any imact!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
4/24/2008 5:14 PM
 

You could try the Friendly Url Provider that I distribute : it's a replacement for the standard DNN Friendly Url Provider and works in the same way, but produces better Urls - but in your case, more importantly, it includes a regex filter to exclude whatever type of request you like from the DNN processing which is causing the problem.

You can read about it at the iFinity Friendly Url Provider for DotNetNuke product page.

-Bruce
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HttpHandlers under DNN 4.7.0HttpHandlers under DNN 4.7.0


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out