-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
DietPi-Software | O!MPD: New (Buster+ARMv6) Lighttpd config breaks "Now Playing" page #2816
Comments
@maartenlangeveld Will have to check what this setting actually does. Also we currently ship an outdated version of O!MPD due to database sync errors with the (that time) current one. But will retest this and perhaps the new version works with new Lighttpd defaults as well. |
Hi @MichaIng, Have just checked latest O!MPD version (git clone from O!MPD github repo). Works fine at first sight. No databases errors. Plays my music catalogue and streams (radio) as well. At first sight seems okay with me. |
@maartenlangeveld I will also test on VM and RPi now. |
Meanwhile has been solved by O!MPD @ArturSierzant (many thanks !) in O!MPD GitHub master |
Jep fixed in latest master, although we generally should go with latest release. Here is how we'll do it: ArturSierzant/OMPD#86 (comment) Further optimisations: ArturSierzant/OMPD#86 (comment) |
PR up: #2884 |
@MichaIng
Hi Micha,
With the new lighttpd version in v6.24, there is also a new lighhtpd.conf config file shipped.
This breaks one specific webpage ('Now Playing') under a specific condition (empty playlist): "400 Bad Request" when clicking ('Now Playing') oon O!MPD startpage.
After som trial and error I managed to discover which element in the new config file was the cause. Just to let you know:
New version lighttpd added following lines to lighttpd.conf.
When I disable "url-ctrls-reject" the "Now Playing" page in O!MPD page loads again when playlist is empty. If enabled (as default with new lighttpd versions), I get ""400 Bad Request" error message.
The text was updated successfully, but these errors were encountered: