-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gen-delims (brackets) not escaped in href #45
Comments
MkfsSion
added a commit
to MkfsSion/nginx-dav-ext-module
that referenced
this issue
Feb 23, 2023
* Fixes arut#45 Signed-off-by: MkfsSion <[email protected]>
Why does issue is still open, if it was fixed in ? |
fjqingyou
pushed a commit
to fjqingyou/nginx-dav-ext-module
that referenced
this issue
May 18, 2024
* Fixes arut#45 Signed-off-by: MkfsSion <[email protected]>
3 tasks
I also encountered this problem, how to solve it? |
This repository is already dead. It has been dead for six years. Please accept my condolences. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When files with brackets (
[
,]
) in their file names are listed, those characters are not escaped, causing some clients to ignore them. (This was previously pointed out as a bug in davfs2, but found to be on nginx-dav-ext-module's side).Characters not in
pchar
(fromSimple-ref
viapath-absolute
andsegment
) should be escaped per RFCs 4918 and 3986.A working solution is to replace, in the two calls to
ngx_escape_uri
inngx_http_dav_ext_module.c
,NGX_ESCAPE_URI
withNGX_ESCAPE_URI_PATH
, which is a new version that'd need to be introduced in ngx_string.[hc]. It leaves the slashes unharmed but escapes almost everything else (so it's a copy ofNGX_ESCAPE_ARGS
but with the slash left unescaped). I can't really propose that change to upstream before dav-ext-module acknowledges its use case, so: would that work for you?(This is a successor to #6, which started escaping but only solved the cases many more clients are sensitive to, but not all the cases of not being
pchar
.)The text was updated successfully, but these errors were encountered: