Cancelled

WebDAV Server

I was asked to develop an centralized archiving program on a server. My idea is, to use a WebDAV connection for the clients to store the documents. I'm yet not familiar with the WebDAV protocol and how to implement in RealBasic.

Can somebody help me and develop a basic WebDAV server for me providing base functionalities (I will implement the complete set of the archiving requirements by myself) for handling the client sessions according to the following RFC's:

RFC 2291 – Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web

RFC 2518 – HTTP Extensions for Distributed Authoring – WEBDAV

RFC 3253 – Versioning Extensions to WebDAV

RFC 3648 – Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol

RFC 3744 – Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol

RFC 4316 – Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties

RFC 4331 – Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections

RFC 4437 – Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources

RFC 4709 - Mounting Web Distributed Authoring and Versioning (WebDAV) Servers

RFC 4791 - Calendaring Extensions to WebDAV (CalDAV)

RFC 4918 – HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)

RFC 5323 – Web Distributed Authoring and Versioning (WebDAV) SEARCH

RFC 5397 - WebDAV Current Principal Extension

RFC 5689 - Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)

RFC 5842 - Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)

Versioning of documents is essential!

The following requests should handled:

PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, DELETE, LOCK and UNLOCK.

For each of the requests a separate function/sub should be used. Each function/sub should call an exit to another sub for real execution of the command on a specified root directory on disk. (This sub will be replaced or extended later on by me).

Of course the connection should be secure (SSL!). Identification via plain login with User-ID and password should be implemented and only requested if the connection is secure (SSL or TLS). Standard should be digest HTTP authentication. Only if this fails a fallback to basic authentication should be possible.

Encoding method parameter information for WebDAVshould encoded in XML ([REC-XML]) in the request entity body is mandatory. Additional encoding in an HTTP header is preferred.

Denial-of-service attacks should be handled.

The developer should be familiar with RealBasic, HTTP and WebDAV protocol extensions. Knowledge about ServerSocket, SSLSocket, XML syntax and XML parsing is required.

Skills: HTML, REALbasic, Web Security, XML

See more: realbasic webdav, webdav realbasic, realbasic webdav server, xml web server, web developer extensions, web developer directory, method web developer, set service resources, extension web developer, extended properties, webdav xml, web developer resources, webdav, unlock store, server move, rfc, rec, quota, digest authentication protocol, dav, collections, authoring, server requested authentication, world server, redirect requests

About the Employer:
( 0 reviews ) Frankenberg, Germany

Project ID: #1097592

3 freelancers are bidding on average €1083 for this job

superior5

I have done similar work before. Please get back to me if the project is still open

€1500 EUR in 20 days
(31 Reviews)
6.8
linuxweb

hello i can start work plz check PM

€1000 EUR in 10 days
(0 Reviews)
0.0
ounis

Check your PM.

€750 EUR in 10 days
(0 Reviews)
0.0