Thank you for writing back Thomas. It seems I did not get that protection since
I am on Ubuntu 14.04.
I am pleased to hear, however, that the installer behavior has improved. Thank
you.
I was on nginx version 1.4.6 and upgraded to 1.12.2 to get support for
dynamically loaded modules.
I am on
@Frak which NGINX are you upgrading from on which OS?
In current versions of the package from 16.04 and later, there is
configuration changes in postinst to *NOT* overwrite index.html if an
index.html exists already in the default docroot.
--
You received this bug notification because you are a
When upgrading nginx, the installer is smart enough to notice that my
configuration files are changed and gives me the option to keep my
modified one, or update it, diff it etc but isn't smart enough to make
a backup of index.html before it overwrites it? How hard is it to do the
same thing for
I'd like to add to this, I installed nginx on my Raspberry Pi and was
using it on my internal network. I'm not an administrator, just a
tinkerer who has no knowledge that the default www share should not be
used. Because of this i've lost my index.html that i was using.
I'd assume there are a lot
I'd like to add to this, I installed nginx on my Raspberry Pi and was
using it on my internal network. I'm not an administrator, just a
tinkerer who has no knowledge that the default www share should not be
used. Because of this i've lost my index.html that i was using.
I'd assume there are a lot
This isn't fixed - it's marked Fix Released in Debian only because of
Debian considering this Won't Fix.
There's a reason that we say that certain spaces on the file system
aren't for users and this is one of them - this is why I said in my last
post on this even that you should NOT be using the
This isn't fixed - it's marked Fix Released in Debian only because of
Debian considering this Won't Fix.
There's a reason that we say that certain spaces on the file system
aren't for users and this is one of them - this is why I said in my last
post on this even that you should NOT be using the
Ubuntu 15.04 apt upgrades just overwrote my index.html at
/usr/share/nginx/html/index.html
It looks like nginx had an update on 7-20. Regression seems to be
there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Ubuntu 15.04 apt upgrades just overwrote my index.html at
/usr/share/nginx/html/index.html
It looks like nginx had an update on 7-20. Regression seems to be
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Samuel Messner and everyone:
This has not actually been fixed based on the bug. The reason this is
'Fix Released' in Debian here is because Launchpad has the incorrect
logic for the Debian bug. (See
https://bugs.launchpad.net/launchpad/+bug/1413304 for details on the
logic breakage).
From the
Samuel Messner and everyone:
This has not actually been fixed based on the bug. The reason this is
'Fix Released' in Debian here is because Launchpad has the incorrect
logic for the Debian bug. (See
https://bugs.launchpad.net/launchpad/+bug/1413304 for details on the
logic breakage).
From the
This has been fixed for Debian, it should really be fixed for Ubuntu
too. I don't keep the files being served in /usr/share/nginx/www/, but
nginx still overwrote my index.html after an nginx -s reopen. I have a
hard time seeing how this would be intended in any way - this behavior
has the ability
This has been fixed for Debian, it should really be fixed for Ubuntu
too. I don't keep the files being served in /usr/share/nginx/www/, but
nginx still overwrote my index.html after an nginx -s reopen. I have a
hard time seeing how this would be intended in any way - this behavior
has the ability
** Bug watch added: Debian Bug tracker #774464
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
** Also affects: nginx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #774464
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
** Also affects: nginx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774464
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: nginx (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly overwritten
To manage notifications
** Changed in: nginx (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly overwritten
To manage
Apache goes against the Debian policy on this one. They have to because
of some hacks in some plugins that are supposed to enhance security. The
default is simply a default. Some people will actually store websites in
/etc/nginx/www/ on debian systems. There's no way to correct everyone
that isn't
Apache goes against the Debian policy on this one. They have to because
of some hacks in some plugins that are supposed to enhance security. The
default is simply a default. Some people will actually store websites in
/etc/nginx/www/ on debian systems. There's no way to correct everyone
that isn't
Will Ubuntu fix the package, or does it need to be done by the Debian
maintainer?
Whether it needs fixing or not is a matter of debate. Personally, I
agree with you, but this isn't a reason in itself to make a change. I
would prefer to see consensus across Debian and Ubuntu, and am unwilling
to
Will Ubuntu fix the package, or does it need to be done by the Debian
maintainer?
Whether it needs fixing or not is a matter of debate. Personally, I
agree with you, but this isn't a reason in itself to make a change. I
would prefer to see consensus across Debian and Ubuntu, and am unwilling
to
Irrespective of what the default document root is, whether it is
/usr/share/nginx/www or /var/www/html, the issue in this bug report is
whether a user should expect to be able to modify the index.html file in
the default document root and have those changes respected.
If your answer is that the
Irrespective of what the default document root is, whether it is
/usr/share/nginx/www or /var/www/html, the issue in this bug report is
whether a user should expect to be able to modify the index.html file in
the default document root and have those changes respected.
If your answer is that the
I've just noticed this bug.
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files. To serve static files, the document root should be changed.
Somewhere under /srv is suitable under the FHS.
It would be nice if this were documented better somehow (I don't know
how), but this
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files.
Apart from the default ones provided by packaging, of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
I've just noticed this bug.
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files. To serve static files, the document root should be changed.
Somewhere under /srv is suitable under the FHS.
It would be nice if this were documented better somehow (I don't know
how), but this
IMHO, /usr/share/nginx/www/ should never be used to actually serve
files.
Apart from the default ones provided by packaging, of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Thomas - both points well taken, thanks for triaging. (fyi, 1.5.8 and
now 1.5.9 are pulled in on 12.04.3 in AWS at least, so some folks who
bump into this may be not purely stock, but again your point is well
taken that 1.5.x aren't the minimal/initial test-case)
--
You received this bug
Nat:
1.5.8 is not in Ubuntu, and you should not comment on a bug about 1.1.19
when you are using 1.5.8.
I have not yet tested to replicate this, or figure out a solution, but I
have an idea of what needs to be done to fix this. Having said this, I
am a little busy fighting with my system, so
As a suggestion to all affected: I suggest that you do not use the
default document root (/usr/share/nginx/www/) for your files, and
instead use a different document root for your sites. By using the
default document root, you are inviting issues such as these to occur.
I also suggest that you
happened to me twice, most recently Ubuntu 12.04.3 upgrading Nginx to
1.5.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly overwritten
To manage
Confirmed because of duplicate bug #1245827
** Changed in: nginx (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly
This just happened to me as well.. Ubuntu 12.04, Nginx 1.1.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly overwritten
To manage notifications about
To stress - it's a very serious issue, which took down a server and also
meant code loss (as, unfortunately, the backup wasn't up to date). Can
you please investigate? I'm concerned about it happening again.
Should I open a new bug, or can you re-open an expired one? Thanks.
--
You received
[Expired for nginx (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nginx (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Can you please add details of which Ubuntu version and which NGINX
version you are using?
** Changed in: nginx (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
36 matches
Mail list logo
