/usr/share/doc/apache2-doc/cgi-examples/printenv:
print Content-type: text/plain; charset=iso-8859-1\n\n;
charset assumptions?
But mainly, this can be simplified to:
for (sort keys %ENV) {
$val = $ENV{$_};
$val =~ s|\n|\\n|g;
$val =~ s||\\|g;
print $_=\${val}\\n;
}
--
To
Package: apache2.2-common
Version: 2.2.6-3
I have discovered a bug in the Debian apache2 and/or php packages.
Consider the following .htaccess file,
#SetEnvif User-Agent . ban
#SetEnv ban
Order Allow,Deny
Allow from all
Deny from env=ban
Looking in error.log, if you uncomment the first line,
Package: apache2
Version: 2.2.6-3
Severity: minor
Instead of the user having to search Google for ways to fix
# apache2ctl start
apache2: Could not reliably determine the server's fully qualified
domain name, using 127.0.0.1 for ServerName
Could we instead have a configuration item
[ ]use
I see 301s 403s 200s... in my twisted homebrew mediawiki .htaccess
mess's logs that now slip from my brain as I moved on to a different project...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sorry, I didn't notice.
Actually they're easy to spot using e.g.,
emacs' show-trailing-whitespace.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
!Common Problems
!===
!
!1) Error message Could not determine the server's fully qualified domain name,
!using 127.0.0.1 for ServerName during start
!
!This can usually be ignored but it means that Apache httpd was unable to obtain
!a fully-qualified hostname by doing a reverse lookup
Package: apache2-utils
X-debbugs-cc: fabbi...@fabbione.net
Version: 2.2.11-3
File: /usr/share/man/man8/check_forensic.8.gz
Tags: patch
I hope this is what check_forensic does. At least that is what the
source code says it does.
$ zdiff -u /usr/share/man/man8/check_forensic.8.gz
Package: apache2.2-common
Version: 2.2.11-3
Severity: minor
File: /usr/sbin/apache2ctl
Please make sure help is mentioned in both cases below, so that there
is no longer the two lines with just 0.
# for i in -- ''; do for c in wc 'grep -ic help'; do k=apache2ctl ${i}help
21|$c;echo \# $k; eval
I really don't understand the usefulness of this.
You have two different types of help output.
Depending on which one a users triggers, he will never know about the
other.
On the man page you document a help command, but the Usage messages,
both of them, make no mention of it. You must admit that
OK, hope I don't break anything.
# find /etc/apache
/etc/apache
/etc/apache/conf.d
# rm -r /etc/apache
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: apache2.2-common
Version: 2.2.13-2
Severity: wishlist
Seen on upgrade:
Setting up apache2.2-common (2.2.13-2) ...
insserv: warning: current start runlevel(s) (empty) of script `apache2'
overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
Package: apache2.2-common
Version: 2.2.22-2
Severity: grave
Starting web server: apache2/usr/sbin/apache2: symbol lookup error:
/usr/sbin/apache2: undefined symbol: pcre_info
Action 'start' failed.
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of
I have an idea,
all /etc/init.d/ script packages should test to see they actually can be
started and stopped before their debs get shipped.
Hmmm, and all bin/ programs should given a test run too... to at least
see they can print --version without segfaulting etc.
Hmmm, all even more important
It doesn't matter who is to blame.
A simple /etc/init.d/... start test could catch such grave bugs before
they hit the user.
Who is to blame could be figured out internally.
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: apache2
Version: 2.4.1-2
Severity: grave
# a2enmod php5
Enabling module php5.
To activate the new configuration, you need to run:
service apache2 restart
# service apache2 restart
apache2: Syntax error on line 161 of /etc/apache2/apache2.conf: Syntax error on
line 1 of
Package: apache2
Version: 2.4.4-2
Severity: wishlist
I would just like to note that during upgrade the user's httpd.conf is
thrown away as if there is no danger he had customized it.
Also whatever messages you were trying to tell the user upon apt-get
upgrade flies off the screen and is not
Yes so I decided to reinstall from scratch and now index.php is being
interpreted as plain text so I cannot figure out how to make it
interpreted as PHP here with apache 2.4 in Debian and any searches just
give advice for older versions of apache.
--
To UNSUBSCRIBE, email to
It turns out one needs to install
libapache2-mod-php5
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707759
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: apache2
Version: 2.4.4-6
Severity: minor
I'm telling you guys, not everybody runs apache2 24/7/365 days a year,
so please double check if it was running first (before the upgrade
started) before causing these error messages during upgrades!
...
Replacing config file
By the way, we here doing apt upgrades don't necessarily understand what
apache2-maintscript-helper invoked from a modified environment.
Please hint required arguments manually
is all about.
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe.
Package: apache2-doc
Version: 2.4.6-3
Severity: wishlist
File: /usr/share/doc/apache2-doc/manual/en/mod/mod_setenvif.html
file:///usr/share/doc/apache2-doc/manual/en/mod/mod_setenvif.html
mentions If twice,
but does not link them to
file:///usr/share/doc/apache2-doc/manual/en/mod/core.html#if
21 matches
Mail list logo
