Ludek -
I have a temporary workaround to this problem. Here's what I did:
First off, I made a duplicate of the web.config <httpHandlers> entry for "CrystalImageHandler.aspx", and removed the ".aspx". So now there's 2 entries - one with ".aspx" and one without.
I did the same with the <handlers> entry for "CrystalImageHandler.aspx_GET". I copied the entry, and replaced ".aspx" with "" (it's in there twice).
I thought this would solve the problem, and I still think it should, but I had to do one more thing.
I disassembled your CrystalImageHandler class and copied it into a new class of my own. There's a couple of references to internal constants, so I copied them into my class also, so it would compile. Then I changed the web.config entries (mentioned above) to point to my new version of the handler.
Now everything works fine. I get images showing up in the viewer like they should.
I can't explain why I had to recompile your CrystalImageHandler class. I didn't change anything, other than copying the constant so it would compile. I still think I shouldn't have to do this, and maybe I don't - maybe I just missed something somewhere. In any case, it works.
What would you like me to do with this information? I could post the code for the CrystalImageHandler class, but I suspect that's a violation of some copyright or something. I could just give instructions for how to do it - basically post this in the other thread also.
Another option is I can rewrite the CrystalImageHandler class myself from scratch, now that I know what's going on. It's a small class and I could rewrite it easily, using the names and logic the way I would normally do something like this. It would be essentially the same - just in my own words. If that would get around any copyright issues.
Let me know what you want me to do.
Dan
