We have a module that displays an image using a simple aspx page that calls the Response.BinaryWrite method. The module is installed on a page in a child portal. All works well when we are logged in with a SuperUser account. However, when the same page is loaded when logged in as the child portal administrator (or any other user set up on the child portal) the image displays in Firefox and not in IE7 but in both browsers on the very next click we get redirected to the login page. Go back and try it as a SuperUser and the page is fine and we can navigate to any other page.

We've changed the BinaryWrite to include the length etc as we thought that the http response header may be getting corrupted - but if it was, the image would not display. Is anything being written to a temp folder that we need ASP.NET write access to?

I found the solution in a previous posting about cookie problems http://www.dotnetnuke.com/Community/Forums/tabid/795/postid/36672/Default.aspx

The portalid and tabid need to be added to the querystring that calls the helperfile as in ='<%# Eval("ImageID", "Property_Image_Display.aspx?pimd={0}&size=Full&portalid=1&tabid=97") %>

everything then works perfectly.

ImageUrl