On 06.04.2015 14:36, Eric Covener wrote:
> On Sun, Apr 5, 2015 at 10:20 AM, Sebastian Pipping
> wrote:
>> Has it lived on until Apache 2.2? Until 2.4?
>>
>> How does the hacked workaround work?
>
> It's still present. If no handler is explicitly set, the content-type
> is copied over as the han
On Sun, Apr 5, 2015 at 10:20 AM, Sebastian Pipping
wrote:
> Has it lived on until Apache 2.2? Until 2.4?
>
> How does the hacked workaround work?
It's still present. If no handler is explicitly set, the content-type
is copied over as the handler.
A module can either check for a real or "magic"
Hello Daniel,
On 06.04.2015 11:47, Daniel wrote:
> You can review that in the documentation too:
> http://httpd.apache.org/docs/current/mod/mod_mime.html
I'm aware of that page, but I don't see answers to my questions on that
page.
Best,
Sebastian
--
Sebastian,
You can review that in the documentation too:
http://httpd.apache.org/docs/current/mod/mod_mime.html
Regards
2015-04-05 16:20 GMT+02:00 Sebastian Pipping :
> Hello Nick,
>
>
> On 05.04.2015 13:36, Nick Kew wrote:
> > Apache 1.0 had no AddHandler, so people used AddType as a hacked
>
Hello Nick,
On 05.04.2015 13:36, Nick Kew wrote:
> Apache 1.0 had no AddHandler, so people used AddType as a hacked
> workaround. Apache 1.1 introduced AddHandler, but the AddType
> hack lived on as a zombie.
Has it lived on until Apache 2.2? Until 2.4?
How does the hacked workaround work?
T
On Sun, 2015-04-05 at 01:21 +0200, Sebastian Pipping wrote:
> [chop]
It's historic.
Apache 1.0 had no AddHandler, so people used AddType as a hacked
workaround. Apache 1.1 introduced AddHandler, but the AddType
hack lived on as a zombie. There are a lot of such zombies around:
for example, alm
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
