komga
komga copied to clipboard
Published
20 hours ago •
gotson
gotson
Komga doesn't log Tomcat errors
Steps to reproduce
- Install komga
- Set up komga behind an nginx proxy
-
curl -u <auth> 'https://<url/basePath>/opds/v1.2/books/<book ID>/path/<... file path>'(file path includes spaces / other special characters) - Observe the following output of this API matches tomcat's default:
<!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html>
Expected behavior
Logs should indicate why tomcat rejected the request. There's no way to set up debug logs for komga's internal HTTP server (Tomcat). This makes it very difficult to debug integration between my reverse proxy (nginx) and komga. It's really not clear at all why the setup works fine for most of komga but just doesn't work at all for opds.
Actual behavior
There are no logs at all indicating there was any kind of error.
Logs
No response
Komga version
1.11.1
Operating system
NixOS
Installation method
jar
Other details
No response
Acknowledgements
- [X] I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I have checked the FAQ.
- [X] I have updated the app to the latest version.
- [X] I will fill out all of the requested information in this form.
