After a long hiatus, I’m back on the project… the code has been upgraded to VS 2005

https://sourceforge.net/projects/webdav/

Comments and suggestions welcome!

Germinal

I want to send documents generated by a buisiness process to different clients by FTP over SSL. That applicaion is working fine. But a few of the clients do not have FTP server but using secure HTTP (WebDAV). I need to copy files from folders on local drive or IIS virtual folders to remote web site folders.

The code I found on MSDN is for copying files from one folder to another on the same web site. In my case I need to copy it either from a local folder or virtual folder in localhost. In the MSDN code I couldn’t figure out a way of providing different credential for accessing resources from localhost and remote host.
Can someone help me to fix the code. Or can someone suggest a different way of doing it in .NET?

[STAThread]
static void Main(string[] args)
{
System.Net.HttpWebRequest Request;
System.Net.WebResponse Response;
System.Net.CredentialCache MyCredentialCache;
string strSourceURI = “http://localhost/Extracts/Client1/test.csv”;
string strDestURI = “https://200.150.100.50/Uploads/test.csv”;
string strUserName = “UserName”;
string strPassword = “password”;
string strDomain = “Domain”;

try
{
// Create a new CredentialCache object and fill it with the network
// credentials required to access the server.
MyCredentialCache = new System.Net.CredentialCache();
MyCredentialCache.Add( new System.Uri(strSourceURI),
“NTLM”,
new System.Net.NetworkCredential(strUserName, strPassword, strDomain)
);

// Create the HttpWebRequest object.
Request = (System.Net.HttpWebRequest)HttpWebRequest.Create(strSourceURI);

// Add the network credentials to the request.
Request.Credentials = MyCredentialCache;

// Specify the COPY method.
Request.Method = “COPY”;

// Specify the destination URI.
Request.Headers.Add(”Destination”, strDestURI);

// Specify that if a resource already exists at the
// destination URI, it will not be overwritten. The
// server would return a 412 Precondition Failed status code.
Request.Headers.Add(”Overwrite”, “F”);

// Send the COPY method request.
Response = (System.Net.HttpWebResponse)Request.GetResponse();

// Close the HttpWebResponse object.
Response.Close();

Console.WriteLine(”Item successfully copied.”);

}
catch(Exception ex)
{
// Catch any exceptions. Any error codes from the COPY
// method request on the server will be caught here, also.
Console.WriteLine(ex.Message);
}
}
}

Many thanks.

Just thought I would let you know that I have just posted a post on my blog about C# webdav server with SQL backend. I have included the full source so it may be useful to anyone wanting to have a look at how you might go about building something like this. You can check it out at:

http://thehojusaram.blogspot.com/2007/06/c-webdav-server-with-sql-backend-source.html

Thanks

I’ve no doubt there’s better code out there but it may give someone a head start.

I think I’ve the answer to a couple of the questions posted here. One is about being able to use a pretty file list that Excel and Word present when interacting with Sharepoint. The short answer is that you can’t. Although Sharepoint is a WebDAV server, it’s also Frontpage server and, in fact, the Office tools use the Frontpage RPC protocol when communicating with Sharepoint. You can see this if you install Fiddler2 (www.fiddler2.com) a free local proxy implemented by a Microsoft employee that allows you to see all headers and body information sent to and received from an HTTP server. Because this is a proprietary protocol, Microsoft can and do extend it to do things that are useful to them such as return a nice file listing.

Whenever any of Microsoft’s re-directors are used they will default to use Frontpage and this probably explains why the MS header must be returned in response to the OPTIONS verb.

One of the regular question is about installing a WebDAV server. The example WebDAV server in the CodeProject article can be installed either at an IIS root or at a virtual directory. In principle it shouldn’t matter where the WebDAV is installed. The Microsoft WebDAV clients will issue an OPTIONS request to the URL specified and issue a PROPFIND if the OPTIONS response is satisfactory. If it’s not, they will then query the web server root. The chances are that this will generate a good response and so Excel or Word will try to work with it though the result amy not be what you expect.

As suggested here, the WebDAV server is implemented as a IhttpHandler so that the WebDAV serve can be installed using a wildcard map.