如何根据用户登录重定向 Lighttpd webdav 挂载
我已启用 lighttpd mod_webdav 模块并设置 http://website.com/webdav 的 webdav 挂载点使用以下 lighttpd.conf 条目:
$["remoteip"] == "www.website.com" {
alias.url += (
"/webdav" => "/var/www/htdocs/webdav",
)
$HTTP["url"] =~ "^webdav($|/)" {
dir-listing.activate = "enable"
webdav.activate = "enable"
webdav.is-readonly = "disable"
auth.backend = "htpasswd"
auth.backend.htpasswd.userfile = "/var/www/htdocs/passwd.dav"
auth.require = ("" => "method" => "basic",
"realm" => "webdav",
"require" => "valid-user" ) )
}
}
这为所有 webdav 用户提供相同的目录。
但是,我想根据 http://website.com/webdav 重定向到特定的子目录webdav 用户名。
例如:
用户以 user1 身份登录,当访问 http:// 时,他/她会看到 htdocs/webdav/user1 website.com/webdav 或者
用户以user2身份登录,他/她在访问http://website时会看到htdocs/webdav/user2。 com/webdav
这可以做到吗?
谢谢
I have enabled the lighttpd mod_webdav module and set up a webdav mount point of http://website.com/webdav using the following lighttpd.conf entry:
$["remoteip"] == "www.website.com" {
alias.url += (
"/webdav" => "/var/www/htdocs/webdav",
)
$HTTP["url"] =~ "^webdav($|/)" {
dir-listing.activate = "enable"
webdav.activate = "enable"
webdav.is-readonly = "disable"
auth.backend = "htpasswd"
auth.backend.htpasswd.userfile = "/var/www/htdocs/passwd.dav"
auth.require = ("" => "method" => "basic",
"realm" => "webdav",
"require" => "valid-user" ) )
}
}
This gives the same directory for all webdav users.
However, I would like to make http://website.com/webdav redirect to a particular subdirectory based on the webdav user name.
For example:
user logs in as user1, he/she sees htdocs/webdav/user1 when going to http://website.com/webdav
oruser logs in as user2, he/she sees htdocs/webdav/user2 when going to http://website.com/webdav
Can this be done?
Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
尽管 HTTP 和 WebDAV 允许这样做,但流行的客户端实际上并不遵循重定向。 结果是Windows客户端、os/x客户端等客户端无法直接连接到该url。
Even though HTTP and WebDAV allows it, popular clients don't actually follow redirects. The result is that clients such as the windows client, os/x client can't connect to the url directly..