webdav issue on PUT

Open
#243 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
apache, docker
Domain
backend, devops

Research direction

Start by reproducing the PUT request against the docker-library/httpd image based on Debian bookworm, then inspect the Apache logs around /var/lib/dav/DavLock and the reported /po.txt.lock path. Check the installed APR and APR-util packages and the WebDAV lock configuration; done means identifying the cause of the 400 response and documenting a confirmed fix or required configuration.

Written by the indexing model from the issue text.

Description

Hello, I'm running a webdav server using this image http:bookworm as base.

When I try to PUT a file with:

curl -T po.txt http://myserver.me/dir/

I get:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
</p>
</body></html>

And the log from the server is:

[Mon Nov 13 14:45:07.242571 2023] [mpm_event:notice] [pid 1:tid 140536338677056] AH00489: Apache/2.4.57 (Unix) OpenSSL/1.1.1n configured -- resuming normal operations
[Mon Nov 13 14:45:07.242576 2023] [mpm_event:info] [pid 1:tid 140536338677056] AH00490: Server built: Jun 13 2023 06:36:54
[Mon Nov 13 14:45:07.242543 2023] [mpm_event:debug] [pid 1:tid 140536338677056] event.c(740): Child 2 started: pid 15, gen 0, active 3/16, total 3/3/16
[Mon Nov 13 14:45:07.242571 2023] [mpm_event:notice] [pid 1:tid 140536338677056] AH00489: Apache/2.4.57 (Unix) OpenSSL/1.1.1n configured -- resuming normal operations
[Mon Nov 13 14:45:07.242576 2023] [mpm_event:info] [pid 1:tid 140536338677056] AH00490: Server built: Jun 13 2023 06:36:54
[Mon Nov 13 14:45:07.242623 2023] [core:notice] [pid 1:tid 140536338677056] AH00094: Command line: 'httpd -D FOREGROUND'
[Mon Nov 13 14:45:07.242633 2023] [core:debug] [pid 1:tid 140536338677056] log.c(1570): AH02639: Using SO_REUSEPORT: yes (1)
[Mon Nov 13 14:45:07.242623 2023] [core:notice] [pid 1:tid 140536338677056] AH00094: Command line: 'httpd -D FOREGROUND'
[Mon Nov 13 14:45:07.242633 2023] [core:debug] [pid 1:tid 140536338677056] log.c(1570): AH02639: Using SO_REUSEPORT: yes (1)
[Mon Nov 13 14:45:07.242904 2023] [mpm_event:debug] [pid 13:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:07.242904 2023] [mpm_event:debug] [pid 13:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:07.243825 2023] [mpm_event:debug] [pid 15:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:07.243825 2023] [mpm_event:debug] [pid 15:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:07.244010 2023] [mpm_event:debug] [pid 14:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:07.244010 2023] [mpm_event:debug] [pid 14:tid 140536332662528] event.c(2401): AH02471: start_threads: Using epoll (wakeable)
[Mon Nov 13 14:45:48.061367 2023] [authz_core:debug] [pid 13:tid 140536324269824] mod_authz_core.c(815): [client 10.42.0.0:21709] AH01626: authorization result of Require all granted: granted
[Mon Nov 13 14:45:48.061462 2023] [authz_core:debug] [pid 13:tid 140536324269824] mod_authz_core.c(815): [client 10.42.0.0:21709] AH01626: authorization result of <RequireAny>: granted
[Mon Nov 13 14:45:48.061367 2023] [authz_core:debug] [pid 13:tid 140536324269824] mod_authz_core.c(815): [client 10.42.0.0:21709] AH01626: authorization result of Require all granted: granted
[Mon Nov 13 14:45:48.061462 2023] [authz_core:debug] [pid 13:tid 140536324269824] mod_authz_core.c(815): [client 10.42.0.0:21709] AH01626: authorization result of <RequireAny>: granted
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
[Mon Nov 13 14:45:48.072406 2023] [:error] [pid 13:tid 140536324269824] AH: ctx->lock_filename: /po.txt.lock.
[Mon Nov 13 14:45:48.072406 2023] [:error] [pid 13:tid 140536324269824] AH: ctx->lock_filename: /po.txt.lock.
[Mon Nov 13 14:45:48.072481 2023] [:error] [pid 13:tid 140536324269824] AH: Unable to open lock file /po.txt.lock.
[Mon Nov 13 14:45:48.072481 2023] [:error] [pid 13:tid 140536324269824] AH: Unable to open lock file /po.txt.lock.
[Mon Nov 13 14:45:48.089338 2023] [dav:error] [pid 13:tid 140536324269824] (2)No such file or directory: [client 10.42.0.0:21709] An error occurred while reading the request body (URI: /dir/po.txt)  [400, #0]
[Mon Nov 13 14:45:48.089338 2023] [dav:error] [pid 13:tid 140536324269824] (2)No such file or directory: [client 10.42.0.0:21709] An error occurred while reading the request body (URI: /dir/po.txt)  [400, #0]

When I created the image I installed the apr and aprutil packages with this line:

apt-get install -y libtool libaprutil1-dev libapr1-dev libaprutil1 libapr1

I saw the line BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format may be linked to this issue, but I'm on debian bookworm.
Any hint about what may be the problem?
Thanks

Dominant language
Dockerfile
Stars
319
Forks
342
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/httpd

All issues in docker-library/httpd

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.