上传 IIS 7,保存到子文件夹
Uploadify 适用于 Visual Studio,但不适用于 IIS 7(相同的计算机),使用表单身份验证。有没有人有 IIS 7 的有效 uploadify 配置,并将其保存到子文件夹中?
我使用 Uploadify jQuery 控件进行客户端上传。
我认为我的 IIS 7 配置有问题。 uploadify POST 立即返回 HTTP 1.1 302 Found,返回到我的登录页面。
我尝试使用位置节点(配置...位置)允许匿名访问上传部分(子文件夹)以及处理 web.config 中图像的页面(脚本)。看来 Uploadify 帖子立即被屏蔽了。
同样,仅使用 Visual Studio 2008 就可以正常工作,但是当我在同一台计算机上运行该网站时,我得到了重定向。
非常欢迎您的想法/想法!
Uploadify works for Visual Studio but not for IIS 7 (same machines), using Forms authentication. Does anyone have a working uploadify configuration for IIS 7 where they save to a subfolder?
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!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
似乎许多嵌套母版页都包含表单身份验证代码以确保用户经过身份验证。这是重定向的来源......
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 ...
我和你有同样的问题。检查
*.axd
脚本的路径。当您有像uploader.axd
这样的路径时,上传程序只能在 root 中正常工作。尝试像这样带有斜杠的路径 ->/uploader.axd
。I had same problem as you. Check path of your
*.axd
script. When you have path likeuploader.axd
uploader work fine only in root. Try path with slash like this ->/uploader.axd
.