Investigate zipdownload error messages flooding the logs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
The error log of our Apache server has been flooded with messages of this kind for some time. I suspect this is caused by zipdownload. Can these messages be disabled?
[Wed Mar 17 13:44:50.619055 2021] [cgi:error] [pid 17800] [client 129.206.xxx.xxx:35826] AH01215: offset: 0, length: 8192, referer: https://heidata.uni-heidelberg.de/dataset.xhtml?persistentId=doi:10.11588/data/HVXXIJ
[Wed Mar 17 13:44:50.621371 2021] [cgi:error] [pid 17800] [client 129.206.xxx.xxx:35826] AH01215: offset: 0, length: 8192, referer: https://heidata.uni-heidelberg.de/dataset.xhtml?persistentId=doi:10.11588/data/HVXXIJ
[Wed Mar 17 13:44:50.621652 2021] [cgi:error] [pid 17800] [client 129.206.xxx.xxx:35826] AH01215: offset: 0, length: 8192, referer: https://heidata.uni-heidelberg.de/dataset.xhtml?persistentId=doi:10.11588/data/HVXXIJ
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the zipdownload path and its logging around the Apache AH01215 messages; the issue does not name a source file or test. Reproduce the flooded logs if possible, then determine whether the messages can be suppressed without breaking zip downloads and document the verification result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100