4 Comments on “What features are missing in Nginx?”
snabb
2012/07/24
It would be great if nginx had dynamic modules. Then OS distributions could package it the same way as for example the uwsgi Debian/Ubuntu package: the user can install exactly the modules that are needed and leave out extra clutter. Also users could compile additional un-packaged modules independently of the main package maintainer.
Currently the package maintainers need to pre-select a list of likely needed modules and build a couple of alternatives, such as nginx-light and nginx-full in Debian/Ubuntu. This is far from optimal.
Make Location directives inherit configurations as in:
location /user {
# Configuration shared by anything that’s “below” /user, unless
# overriden by more specific location section
}
location /user/cgi {
# Configuration that makes it different from what was already configured by “location /user” section.
# Currently “location /usr/cgi” does not inherit what was configured by “location /user”.
# And “include” directive is far from what is considered convinient.
}
It would be great if nginx had dynamic modules. Then OS distributions could package it the same way as for example the uwsgi Debian/Ubuntu package: the user can install exactly the modules that are needed and leave out extra clutter. Also users could compile additional un-packaged modules independently of the main package maintainer.
Currently the package maintainers need to pre-select a list of likely needed modules and build a couple of alternatives, such as nginx-light and nginx-full in Debian/Ubuntu. This is far from optimal.
DSO’s are slated for Nginx 2.0, which should be out next year.
Make Location directives inherit configurations as in:
location /user {
# Configuration shared by anything that’s “below” /user, unless
# overriden by more specific location section
}
location /user/cgi {
# Configuration that makes it different from what was already configured by “location /user” section.
# Currently “location /usr/cgi” does not inherit what was configured by “location /user”.
# And “include” directive is far from what is considered convinient.
}
Ideally, make configuration like
location *.jpg {
…
}
merge with configuration like
location /some/path {
…
}
for url like /some/path/some/file.jpg