I am using the Microsoft ReportViewer control in my custom modules to display reports (for tutorial see here: http://adefwebserver.com/DotNetNukeHELP/Misc/DNNReports/ ). My PageBlaster version is 3.3.2.

The control uses an axd file called Reserved.ReportViewerWebControl.axd to do most of the report rendering. This is set up in web.config in HttpHandlers as follows:

< add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false" / >

With an out-of-the box configuration, PageBlaster blocks the report rendering. I am guessing this has something to do with the axd file. However if I add the following exclude, strange things happen:

< path pattern="ReportViewerWebControl.axd" excludeFrom="All" / >

IE attempts to download ReportViewerWebControl.axd to the desktop. FireFox does not download anything but displays some HTML code inside the report control. See attached screenshots.

The main part of the report control (where the report should appears but which is being blocked) is rendered as an IFrame with the SRC pointed to Reserved.ReportViewerWebControl.axd, e.g.

< iframe src=" /mm/Reserved.ReportViewerWebControl.axd?OpType=DocMapReport&ClientController=dnn_ctr400_Report_EventLog_rpvReport1&ReportUrl=%2fmm%2fReserved.ReportViewerWebControl.axd%3fMode%3dtrue%26ReportI
frameborder="0" id="ReportFramednn_ctr400_Report_EventLog_rpvReport1" name="ReportFramednn_ctr400_Report_EventLog_rpvReport1" style="width:100%;height:100%;border-top:1px Black Solid;display:none;" >< /iframe >

Can you suggest how to get the control to work under PageBlaster?

What happens when you do a pattern like this?

pattern=".*" excludeFrom="All"

If that works then we'll know it is some other request that needs to be excluded.

Do you have the StaticFileHandler for PageBlaster enabled in the httpHandlers section of web.config? If so, you can try switching the relative position in the list of that line in relation to the report viewer handler line.

With < path pattern=".*" excludeFrom="All" / > in the config I get exactly the same behaviour.

I do not have the Snapsis.HttpModules.PageBlaster.StaticFileHandler line enabled in the httpHandlers section of web.config.

Ok, I'm assuming you commented out PageBlaster in the web.config to make sure it works without PageBlaster.

If you exclude everything it leaves very little that PageBlaster may be doing, but it could be the content type not being recognized. Can you monitor the response of that call to ReportViewerWebControl.axd and see if it looks different with PageBlaster running and without?

I'll see if I can try this out in debug mode if you can't see a difference.

Oh, one other thing you can try is to change the attach-filter-early attribute in the Snapsis.PageBlaster.config to true.

Yes, if I comment PageBlaster out in the web.config it works.

I tried switching attach-filter-early attribute from false to true but it made no difference.

I traced the traffic with Fiddler with PB on and off, and there is a difference. When the page is working (PB commented) there are 3 calls to ReportViewerWebControl.axd and the content-type is text/html; charset=utf-8. When PB is uncommented, the 1st call becomes application/x-javascript; charset=utf-8. The 3rd call seems unchanged. Its difficult to describe what happens to the 2nd call - there is a ton of extra traffic which wasn't there when PB was commented.

Can you look at the Fiddler archive I am attaching? I saved it with Fiddler v 2.2.2 against IE 7. It contains both tests as follows:

With PB commented, lines 0-4 show the page with the report on loading OK.
Then PB is uncommented and the page is reopened. Lines 5-9 show the page starting to load up until the point IE asks if I want to download ReportViewerWebControl.axd to the desktop. When I click Save lines 10 onwards happen.

I have attached a new build of PageBlaster that bypasses the setting of the content type if the request is excluded. I'm not sure why I was setting that on exclusions anyway, and it is surprising that I haven't had more problems because of it.

Please give it a try with the ReportViewerWebControl.axd excluded.

OMG, it works! Tested in IE and FF with ReportViewerWebControl.axd excluded and the reports came up perfectly. Great news and thank you so much!

Of course I am now wondering if this DLL is suitable for using on a live site in place of 3.3.2. Is it "finished" or a WIP? Will you be releasing 3.3.7 any time soon? Lastly what has changed between 3.3.2 and 3.3.7.

A problem - not with the ReportViewer but with PB 3.3.7 in general. I getting a lot of pages where the content is complete "gobbledigook" - see below for a small sample:

‹ 4qù ÿí}û–¢Hòðß=çÌ;°îNW÷ZU *jWWíOñ†Š(à­ö›Ó
E@.*îÎ}¯ñ=Ù—ÉE­¾ÚÓ3¿3s¦ZÉŒŒŒŒˆŒˆŒL“÷«2$?éՐ&OwÞ Ò¡H$u‡¢£,‰¢U¾Täî1„·ÝVÕÐ
EkÝÔÓ{ÅYi¢ úü1%ëw
,“ Q¥ÇT|
Ï+Ùüg|!
Ó³Ô¹â¤]Xɏ)’éMXªÑäSˆh莬; ,BÞˆoÃJÈÔCXW×U}ŽTKN!hqÙuÊ°–|“ac(/7€ÙÇX²vùk83 k]> _¥8ž¥*žbº1ðF‡©”;gÈ™
Ãs10ª[­o‘:Óé0£sR†Gñwå:_‹“ŸAªå w]æ©n#NB­[cã4(ŽcÞÉkWÝ<¦zåFíç1+odAó%û¦êZ”î#v{õc歏Îv<Mö¹ÍÁo=MeÅÐ$ðÜñL@#ïT´m rÔ‡~z¯©úÒoó¡gXŽ Ù>HòLp5çC
±dí1åÚŠ,;ghÅ’g)4lŠFMÑðóÞB?Ú·TuûC͵>„

This seems to happen when PB serves the content. Here are the headers of an example:
HTTP/1.1 200 OK
Date: Thu, 30 Apr 2009 10:33:17 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Snapsis-PageBlaster: v:3.3.7;c:m;x:+;r:+
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 9308

I am also getting some client side errors (on pages that do work) such as:
Sys is undefined
WebForm_PostBackOptions is undefined

There were only minor bug fixes between 3.3.2 and 3.3.7

Your latest errors must be from my last change.
Apparently the content type is now not getting set on pages returned from PB cache. I'll get that fixed and test it out.

OK, The problem was in that latest change I made that was causing the Pages delivered from cache not to have the content-encoding set.

This one is tested out and working.

Thanks, this new version seems to be working fine.
Will you be releasing a 3.3.7 version soon, or should I hang on to this DLL? Is it built in Release mode?

Any news on releasing the 3.3.7 version?

Hi John,
Remember this issue I raised a few months back? Well you totally fixed it inside the 3.3.7 version you gave me, however the issue is back again in the newly released 3.4.1 version. I am wondering if it got left out somehow.

Could you look and see if the fix can be included in the latest version? The latest version is also pretty significant for me as it contains the fix for the "System.IO.FileNotFoundException" error.

Many thanks

Hi John, could you take a look at this please?
Thanks

I don't remember what might have been changed (and then changed back) but I made a guess if you want to try out the attached DLL.

Thanks I'll test it. If this helps, this is what the problem is:

I said (on 29 Apr 2009):

I traced the traffic with Fiddler with PB on and off, and there is a difference. When the page is working (PB commented) there are 3 calls to ReportViewerWebControl.axd and the content-type is text/html; charset=utf-8. When PB is uncommented, the 1st call becomes application/x-javascript; charset=utf-8. The 3rd call seems unchanged. Its difficult to describe what happens to the 2nd call - there is a ton of extra traffic which wasn't there when PB was commented.

Then you fixed the problem and said:

I have attached a new build of PageBlaster that bypasses the setting of the content type if the request is excluded. I'm not sure why I was setting that on exclusions anyway, and it is surprising that I haven't had more problems because of it.

That is what I had commented out (and just put back), so it must of became a problem somewhere else, but I'm still not sure why I would set it if PageBlaster has been excluded.

I have tested the attached DLL. It seems to be working fine.

Will you be creating a release anytime soon containing this fix?