Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: error (nike.apache.org: local policy)
Message-ID: <552071EA.2030203@pipping.org>
Date: Sun, 05 Apr 2015 01:21:14 +0200
From: Sebastian Pipping <sebastian@pipping.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: users@httpd.apache.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: [users@httpd] Effect of AddType / Differences of AddType and
 AddHandler

Hello!


I recently learned that both the AddType and AddHandler directives run a
multiple extension approach [1].  So a line like

  AddHandler application/x-httpd-php .php
     ^^^^^^^
could get you into situations where image uploads of files named
"code.php.png" despite ".php" not being the end of the string.  Okay.


I have seen lines like

  AddType application/x-httpd-php .php
     ^^^^
using AddType rather than AddHandler (e.g. at a rather popular German
website called Selfhtml [2]), too.  That's why I'm contacting you.


>From the official AddType docs [3] I was assuming that AddType would
only set the string sent in "Content-type: ..." server response headers,
previously.


To put it into questions:

 * What are the effects of a "AddType ..." line really?

 * What are the differences of AddType and AddHandler?

 * What is the relation of MIME types and handlers in Apache?

 * Are there differences from what Apache 2.2 did compared to 2.4
   in this area of working?


Many thanks in advance for your help!

Best,


Sebastian


[1] https://httpd.apache.org/docs/current/mod/mod_mime.html#multipleext
[2] http://aktuell.de.selfhtml.org/artikel/server/apacheconf/apconf15.htm
[3] https://httpd.apache.org/docs/current/mod/mod_mime.html#addtype

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org