Skip to content
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

index.html breaks webdav #4

Open
Richie765 opened this issue Jan 18, 2019 · 3 comments · May be fixed by #21
Open

index.html breaks webdav #4

Richie765 opened this issue Jan 18, 2019 · 3 comments · May be fixed by #21

Comments

@Richie765
Copy link

Having a file called index.html inside the webdav share will bring sharing to its knees.

To fix this add DirectoryIndex disabled to the config.

See also: https://dimitar.me/upgrading-to-apache-2-4-will-prevent-webdav-listing-of-directories-containing-index-files/

@ricardojlrufino
Copy link

+1

@marianobianchi
Copy link

+1

dkleeman01 added a commit to dkleeman01/docker-webdav that referenced this issue Apr 7, 2020
DirectoryIndex disabled <-- allows index.html files to be in your webdav served folders without that folder being served as blank
See:   http://dimitar.me/upgrading-to-apache-2-4-will-prevent-webdav-listing-of-directories-containing-index-files/
and:   BytemarkHosting#4
brlin-tw added a commit to brlin-tw/docker-webdav that referenced this issue Apr 15, 2020
Fixes BytemarkHosting#4.

Signed-off-by: 林博仁(Buo-ren, Lin) <[email protected]>
@brlin-tw brlin-tw linked a pull request Apr 15, 2020 that will close this issue
@ArneBachmann
Copy link

The workaround of using DirectoryIndex disabled resolves the WebDAV issue, but will break display in a web browser.

I manage contents on my webserver via WebDAV (not FTP), and users watch them via HTML pages. This use case is currently not possible due to this issue! Either WebDAV breaks, or index.html rendering breaks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants