Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1373822 - wrong config option, default_server in nginx.conf
Summary: wrong config option, default_server in nginx.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nginx
Version: 30
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Felix Kaechele
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-07 08:25 UTC by Tuomo Soini
Modified: 2020-05-18 10:46 UTC (History)
10 users (show)

Fixed In Version: nginx-1.18.0-1.fc30 nginx-1.18.0-1.fc31 nginx-1.18.0-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-03 04:40:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tuomo Soini 2016-09-07 08:25:47 UTC
nginx.conf has server configured as default_server.

This is wrong, because that forces every adminstrator to remove that option from nginx.conf to get things working properly with virtual hosts. Unlike apache which searches for first named virtual host if it doesn't find match, nginx uses server marked as default_server when there is no matched hostname.

I suggest removing option default_server from nginx.conf and leaving it up to adminstrator to decide which virtual host is the default_server instead of forcing fallback to package configured web server.

Would removing default_server break initial setup? No. Initial setup works exactly as before, without default_server option.

Benefit from removing default_server from nginx.conf is: administrator can create whole configuration without touching /etc/nginx/nginx.conf by using /etc/nginx/conf.d/*.conf.

This same bug applies to all fedora and epel versions of the nginx package.

Comment 1 Fedora End Of Life 2017-02-28 10:13:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 Daniel 2017-04-23 23:17:10 UTC
This issue should be closed as a duplicate of issue #1220094.

Comment 3 Fedora End Of Life 2018-05-03 09:06:32 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Tuomo Soini 2018-05-03 09:17:32 UTC
Please, remove option default_server from nginx.conf fallback web service!

Comment 5 Jan Kurik 2018-08-14 11:00:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 6 Tuomo Soini 2018-11-19 08:30:35 UTC
This applies to current rawhide. And all fedora provided nginx packages. Plaase fix.

Comment 7 Ben Cotton 2019-02-19 17:11:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 8 Fedora Update System 2020-04-24 03:16:25 UTC
FEDORA-2020-318ce3d301 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-318ce3d301

Comment 9 Fedora Update System 2020-04-24 03:16:25 UTC
FEDORA-2020-b17de7fa07 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b17de7fa07

Comment 10 Fedora Update System 2020-04-24 03:16:26 UTC
FEDORA-2020-78690e2cdd has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-78690e2cdd

Comment 11 Fedora Update System 2020-04-25 04:18:54 UTC
FEDORA-2020-b17de7fa07 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b17de7fa07`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b17de7fa07

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2020-04-25 04:55:27 UTC
FEDORA-2020-318ce3d301 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-318ce3d301`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-318ce3d301

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2020-04-25 12:20:51 UTC
FEDORA-2020-78690e2cdd has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-78690e2cdd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-78690e2cdd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Ben Cotton 2020-04-30 20:11:36 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora Update System 2020-05-03 04:40:42 UTC
FEDORA-2020-318ce3d301 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2020-05-03 04:53:50 UTC
FEDORA-2020-b17de7fa07 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2020-05-03 05:29:33 UTC
FEDORA-2020-78690e2cdd has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.