Hi Laurence,
Probably not too soon. You are the only one that has brought up this specific issue, so I don't want to go through the process of a new release just for this.

OK fair enough. I am very happy to use the DLL you attached in the thread for now, but a couple of questions:

Is it compiled as Release?
Is it a 3.4.2 version plus "my" fix (i.e. no "work in progress" that might cause problems)?

It's compiled in release mode, and there isn't any "work in progress". I'm pretty sure the only difference between yours and 3.4.2 is that one change.

Hi John,

Remember this issue I raised a few months back? Short story is - the issue is back again in the new 3.4.5 release.

The long story is - I reported the issue in 3.3.2, and you fixed it inside a "beta" 3.3.7 version, then issue came back again in the 3.4.1 version. You then fixed it again in a "beta" 3.4.3 version, but in the next official release (3.4.5) the issue is back again.

If you could resolve the issue permanently that would be really great. I am using that "beta" 3.4.3 version on my sites, but would love to be able to keep up with whatever is new in PageBlaster. I guess there must be a good reason for "undoing" whatever fixes the issue!

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.

Hi Laurence,
Yes, I had to remove that "fix" again because of other people having issues with setting the content-type. The trouble is your issue is the only time that fix is needed, but when it is in, it causes problem with just a few other people.

I have tried a completely different way of detecting both issues and attached a new DLL. Please give it a try and let me know if it works in your case.

Yes, this works.

Hi John,
Just let me know you got this - the 3.4.6 DLL that you asked me to try resolves this problem.

Yes, thanks. I'll release a new version before too long. I'm just clearing up some other issues with the latest versions of DNN.