I've got a FileExplorer page that presents users with the files in their home directory using the Custom File Provider example. It works great. However, I'm doing checks to make sure that a person has logged in through our system to make sure they are authenticated so I can show them their home directory.
Since the FileExplorer uses callbacks, doing a response.redirect to the login page gives the "Response.Redirect cannot be called in a Page callback." error.
Originally, I was using this:
I then changed it to:
Response.StatusCode = 302
"302 Moved Temporarily"
Response.RedirectLocation = ConfigurationManager.AppSettings(
However, the FileExplorer doesn't appear to redirect correctly. The test I am performing is simply clicking on a folder in the left hand menu while being logged out. It correctly gives me back the 302 status code and the Location header, but FileExplorer just keeps spinning on the grid side as if it's going to do something. I'm doing most of the testing in IE9.