Yes, you're right, that error was a red herring. Looks like it's expected to get 405 if a dir already exists.
Found this on github:
This issue was fixed in lighttpd 1.4.64 (and would have been fixed sooner if reported to lighttpd developers sooner).