views:

239

answers:

2

I'm using the Uploadify jQuery control for client-side uploads.

I think my IIS 7 configuration has issues with it. The uploadify POST immediately returns a HTTP 1.1 302 Found, back to my login page.

I've tried to allow anonymous access to the uploading section(subfolder) plus the page(script) that processes the image in the web.config, using the location node(configuration ... location). Seems like the Uploadify post is immediately blocked.

Again, this worked fine just using Visual Studio 2008, but when I run the site on the same machine I get the redirect.

Your thoughts/ideas are very welcomed!

A: 

It seems that the many nested master pages included Forms Authentication code to ensure the user was authenticated. This was the source of the redirect ...

Marc
A: 

I had same problem as you. Check path of your *.axd script. When you have path like "uploader.axd" uploader work fine only in root. Try path with slash like this -> "/uploader.axd".

Beatle.cz