{"id":"baksili-webdav-server","name":"webdav-server","homepage":"https://hub.docker.com/r/baksili/webdav-server","repo_url":"https://hub.docker.com/r/baksili/webdav-server","category":"storage","subcategories":[],"tags":["webdav","http","files","storage","server"],"what_it_does":"webdav-server is a WebDAV server package that exposes a filesystem-like interface over HTTP using the WebDAV protocol (methods like PROPFIND/PROPPATCH/PUT/GET/MKCOL, etc.), typically for managing and sharing files and directories via standard WebDAV clients.","use_cases":["Hosting and sharing files via WebDAV-compatible clients (e.g., desktop/mobile sync tools)","Backing storage with an HTTP interface for document collaboration","Implementing enterprise file access where WebDAV is required","Bridging legacy WebDAV clients to an application backend"],"not_for":["High-latency or low-trust deployments without careful access control","Exposing broad filesystem write access to untrusted networks","Applications needing modern GraphQL/REST-only APIs without WebDAV semantics"],"best_when":"You need WebDAV compatibility and can securely front the server with authentication/authorization and TLS, with careful control of the exposed root/paths.","avoid_when":"You cannot enforce strong auth and path restrictions, or you need an API style other than WebDAV.","alternatives":["Nextcloud/ownCloud (if you need a full WebDAV suite)","S3-compatible storage with signed URLs (if WebDAV is not required)","FTP/SFTP gateways (legacy compatibility)","Custom REST API for file operations (if you control clients)"],"af_score":28.2,"security_score":48.0,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:25:14.054591+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["HTTP Basic auth (commonly supported in WebDAV servers, if configured)","Session/cookie-based auth (common pattern, if integrated)","Reverse-proxy auth (e.g., via nginx/Traefik)"],"oauth":false,"scopes":false,"notes":"No package manifest/README details were provided here to confirm exact auth modes. In general, WebDAV servers typically rely on upstream auth (reverse proxy) or built-in HTTP auth configured by the operator; fine-grained scopes are often not intrinsic to WebDAV itself."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted OSS/library-style component; no usage-based pricing information available from provided input."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":28.2,"security_score":48.0,"reliability_score":32.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":40.0,"rate_limit_clarity":0.0,"tls_enforcement":70.0,"auth_strength":50.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"Security depends heavily on operator configuration (TLS termination, authentication, authorization, and path sandboxing). WebDAV writes (PUT/DELETE/MKCOL) are high-risk if misconfigured. TLS enforcement and proper authz are essential; scope granularity is often coarse in WebDAV setups.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["WebDAV error handling and status codes can vary by implementation; agents should not assume consistent structured error bodies.","PUT/MKCOL/etc. are not inherently idempotent across all server setups; retries may cause duplicates or conflicts unless ETags/locking and correct semantics are used.","Path traversal protection and root restriction are critical; misconfiguration can expose unintended filesystem locations.","WebDAV can involve locking and metadata operations (LOCK/UNLOCK) that some clients/implementations treat differently; automated clients should account for these nuances."]}}