Project

General

Profile

Actions

Feature #2951

closed

server.modules docs

Added by Olaf-van-der-Spek almost 5 years ago. Updated almost 5 years ago.

Status:
Invalid
Priority:
Low
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:

Description

These modules are loaded automatically, don't load them yourself:

Is this still true?

https://redmine.lighttpd.net/projects/lighttpd/wiki/Server_modulesDetails

lighttpd.conf:

#server.compat-module-load = "disable"
server.modules += (
"mod_compress",
"mod_dirlisting",
"mod_staticfile",
)


Related issues 1 (0 open1 closed)

Related to Feature #2946: modules.conf order unhelpful (setenv vs. redirect)Fixed2019-04-10Actions
Actions #1

Updated by gstrauss almost 5 years ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Invalid
  • Priority changed from Normal to Low
  • Target version deleted (1.4.x)

Olaf, you should know better than to ask question in a bug report.

See related feature request #2946. Clarifying documentation is not a bug.

Actions #2

Updated by Olaf-van-der-Spek almost 5 years ago

It's not a feature request either is it?

IMO it's a documentation bug.

Actions #3

Updated by gstrauss almost 5 years ago

A bug is something that is broken. Do tell me what is "broken". (You obviously have not tested this) Since you seem to have trouble with that, I'll try to state things differently: your opinions do not qualify for indicating a bug. If you find yourself using "IMO", then please do not file a bug report.

lighttpd will load those modules documented as default modules in Server_modulesDetails whether or not you load those modules manually (unless the behavior is changed by disabling server.compat-module-load).
The "don't load them yourself" note is not a bug, though the reasons behind it may be clarified with #2946 (regarding module ordering). My comments there also apply here:

Thank you for your suggestion. Your suggestion may help improve the documentation. However, this is not a bug. It would be a bug if an incorrect statement was made, and which would then need to be fixed. #1895 was marked invalid for the same reason. Instead, you have suggested an improvement.

If you uncomment #server.compat-module-load = "disable", then you should understand what it does.

If you thought you were cutting edge, you would not be using Debian; Olaf, things that you find "new to you" are frequently old news to others.

Actions #4

Updated by gstrauss almost 5 years ago

  • Related to Feature #2946: modules.conf order unhelpful (setenv vs. redirect) added
Actions #5

Updated by Olaf-van-der-Spek almost 5 years ago

A bug is something that is broken. Do tell me what is "broken".

Docs say: "These modules are loaded automatically, don't load them yourself:"
But then lighttpd.conf loads them explicitly, which seems contradictory to the docs.

unless the behavior is changed by disabling server.compat-module-load

Docs for compat-module-load are lacking too..

Actions #6

Updated by gstrauss almost 5 years ago

I asked:

A bug is something that is broken. Do tell me what is "broken".

You still have not demonstrated broken behavior in lighttpd. Instead, you wrote:

But then lighttpd.conf loads them explicitly, which seems contradictory to the docs.

You seem to be referring to the lighttpd.conf distributed with Debian. What website are you on? I'm pretty sure this is not debian.org.

Actions

Also available in: Atom