-
Posted to
Publishing
by
keithmo
on
07-21-2009, 7:07 PM
Yes, that's the setting. It's also accessible via the "Add/Remove Windows Components" dialog accessed from the "Add/Remove Programs" Control Panel Applet, but it's the exact same setting.
-
Posted to
Publishing
by
keithmo
on
07-20-2009, 6:04 PM
It looks suspiciously like "Allow WebDAV Publishing" is not enabled.
I wonder if having SharePoint "installed but prohibited" is causing some strange interaction. Would it be possible to uninstall SharePoint and try again?
-
Posted to
Publishing
by
keithmo
on
07-20-2009, 3:22 PM
Could you post the exact request you sent and the exact response received?
-
Posted to
IIS7 - General
by
keithmo
on
07-19-2009, 11:46 PM
Actually, it can effect this issue -- these problems can be caused if the "Content-Length:" response header is set incorrectly.
The interaction between the "Content-Length:" and "Connection:" headers and "chunked transfer encoding" is somewhat complex, but if a component sets the "Content-Length:" ...
-
Posted to
IIS7 - General
by
keithmo
on
07-19-2009, 10:25 PM
What type of content are you serving? Static HTML/JPG? ASP.NET? PHP? Custom module/ISAPI/CGI?
-
Posted to
IIS7 - Publishing
by
keithmo
on
07-14-2009, 5:36 PM
Aha... you ran into a bug in which WebDAV was not properly escaping certain special characters (such as ampersands) when they're present in file/directory names.
A hotfix is available to address problem; see KB 957001 for details. This applies to "WebDAV 7.0 for IIS 7.0".
Another option is to upgrade to WebDAV 7.5 for IIS 7.0. ...
-
Posted to
IIS7 - Publishing
by
keithmo
on
07-09-2009, 12:11 PM
Why are you creating a handler for the WebDAV module? WebDAV setup creates this for you.
Exactly what errors do you see?
A copy of your config files (or at least the relevant fragments) would be helpful. A FREB log of the failing request(s) would also be extremely helpful.
-
Posted to
IIS7 - Publishing
by
keithmo
on
07-09-2009, 12:07 PM
A FREB log of the failing request(s) would be very helpful.
Is it possible you have an invalid web.config file in the failing directory?
-
Posted to
IIS7 - Publishing
by
keithmo
on
06-23-2009, 3:25 PM
Validation fails because the web.config conflicts with the FX_schema.xml file installed on the server. You need to update the schema file. I don't know the exact process for this; I hope someone else will chime in with details.
You cannot disable web.config validation, and even if you could, it would be a very bad idea. If not for validation, ...
-
Posted to
IIS7 - Publishing
by
keithmo
on
06-22-2009, 10:27 AM
WebDAV for IIS 7 does not allow anonymous write operations (PUT, DELETE, MOVE, etc).