# How to sponsor a feature request?

**URL:** <https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629>\
**Category:** NGINX\
**Created:** [March 6, 2012, 11:59pm UTC](https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629 "2012-03-06T23:59:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [March 6, 2012, 11:59pm UTC](https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629/1 "2012-03-06T23:59:00Z")

</div>

Hi, I have some interest in being able to use WebDAV in nginx with  
enough conformance to be able to use it for file sharing (I think this  
mainly means support for PROPFIND and OPTIONS ?)

Is it affordable to either “encourage” development of this feature, or  
are their regular people who can pickup development jobs like this?

I have had a brief look at what is required (mostly by comparing to the  
various PHP/Perl workarounds) and it mostly looks straightforward  
(especially if it’s acceptable to cheat and assume that allprop is in  
effect and all properties are always returned)

Is there a recommended way to progess? Just for reference, I’m not a  
huge business with big pockets, so please keep suggestions moderate?

Thanks

Ed W

---

<div class="post-metadata">

**Author:** ![ewildgoose](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/bcef8e/32.png) [@ewildgoose](https://www.ruby-forum.com/u/ewildgoose)\
**Post date:** [March 7, 2012, 12:47am UTC](https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629/2 "2012-03-07T00:47:56Z")

</div>

Hello!

On Tue, Mar 06, 2012 at 10:58:49PM +0000, Ed W wrote:

> straightforward (especially if it’s acceptable to cheat and assume  
> that allprop is in effect and all properties are always returned)
> 
> Is there a recommended way to progess? Just for reference, I’m not  
> a huge business with big pockets, so please keep suggestions  
> moderate?

You may try Roman A.'s module:

> **[GitHub - arut/nginx-dav-ext-module: nginx WebDAV PROPFIND,OPTIONS,LOCK,UNLOCK support](https://github.com/arut/nginx-dav-ext-module)**
>
> nginx WebDAV PROPFIND,OPTIONS,LOCK,UNLOCK support

Maxim D.

---

<div class="post-metadata">

**Author:** ![ewildgoose](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/bcef8e/32.png) [@ewildgoose](https://www.ruby-forum.com/u/ewildgoose)\
**Post date:** [March 7, 2012, 4:11am UTC](https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629/3 "2012-03-07T04:11:27Z")

</div>

On 06/03/2012 23:47, Maxim D. wrote:

> > this?  
> > [GitHub - arut/nginx-dav-ext-module: nginx WebDAV PROPFIND,OPTIONS,LOCK,UNLOCK support · GitHub](https://github.com/arut/nginx-dav-ext-module)
> 
> Maxim D.

Oh cool. Thanks

Forgive me one more question:

The documentation gives examples of webdav permissions such as:  
dav\_access user:rw group:rw all:r;

What do these groups actually refer to? Is this a straight mapping to  
unix groups/users?

Ideally my users have login tokens which are their email addresses. Any  
suggestions on how to set auth access to users and groups of users given  
they don’t have local unix accounts?

Thanks

Ed W

---

<div class="post-metadata">

**Author:** ![ewildgoose](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/bcef8e/32.png) [@ewildgoose](https://www.ruby-forum.com/u/ewildgoose)\
**Post date:** [March 7, 2012, 10:42am UTC](https://www.ruby-forum.com/t/how-to-sponsor-a-feature-request/217629/4 "2012-03-07T10:42:53Z")

</div>

Hello!

On Wed, Mar 07, 2012 at 03:10:57AM +0000, Ed W wrote:

> > > or are their regular people who can pickup development jobs like  
> > > You may try Roman A.'s module:  
> > > The documentation gives examples of webdav permissions such as:  
> > > dav\_access user:rw group:rw all:r;
> 
> What do these groups actually refer to? Is this a straight mapping  
> to unix groups/users?

This is about chmod on files created (that is, the above means  
“chmod 0664”), it has nothing to do with particular user names.  
All created files will be owner by nginx user (the one set with  
“user” directive, see [Core functionality](http://nginx.org/r/user)).

> Ideally my users have login tokens which are their email addresses.  
> Any suggestions on how to set auth access to users and groups of  
> users given they don’t have local unix accounts?

Simpliest solution is to use auth basic module, see  
[Module ngx\_http\_auth\_basic\_module](http://nginx.org/r/auth_basic).

Maxim D.