Hi,
> It looks like mod_actions does not recognize r->handler set to "" --
> when r->handler is NULL, he will look directly to r->content_type, so
> that may be a potential way to still handle content-type based
> "dispatch" without having the content-type sit in r->handler.
What you suggest woul
Hi there,
>> As an httpd user who's reading this proposal: Currently, I like to
>> configure PHP in combination with Apache in such a way that I set the
>> content type and then have Action application/x-httpd-php ... I don't
>> want to use AddHandler, since then Apache also processes files ending
On Mon, Jul 1, 2013 at 12:29 PM, Eric Covener wrote:
> On Mon, Jul 1, 2013 at 12:16 PM, Christian Seiler wrote:
>> Hi there,
>>
>>
>>> All releases still have what I guess is an old pre-SetHandler
>>> mechanism to allow content type -> handler mappings. If no r->handler
>>> has been set, but a co
On Mon, Jul 1, 2013 at 12:16 PM, Christian Seiler wrote:
> Hi there,
>
>
>> All releases still have what I guess is an old pre-SetHandler
>> mechanism to allow content type -> handler mappings. If no r->handler
>> has been set, but a content-type has, the content-type is copied to
>> r->handler.
>
Hi there,
All releases still have what I guess is an old pre-SetHandler
mechanism to allow content type -> handler mappings. If no r->handler
has been set, but a content-type has, the content-type is copied to
r->handler.
As an httpd user who's reading this proposal: Currently, I like to
confi
On Jun 30, 2013, at 3:47 PM, Eric Covener wrote:
>
> Maybe something to consider zapping from just trunk?
>
++1.
On Sun, Jun 30, 2013 at 3:48 PM, Joseph Schaefer wrote:
> The directory handling still relies on this.
Other *_MAGIC_TYPES do too, but I'm guessing they could be boiled down
to just r->handler.
The directory handling still relies on this.
Sent from my iPhone
On Jun 30, 2013, at 3:47 PM, Eric Covener wrote:
> All releases still have what I guess is an old pre-SetHandler
> mechanism to allow content type -> handler mappings. If no r->handler
> has been set, but a content-type has, the c
All releases still have what I guess is an old pre-SetHandler
mechanism to allow content type -> handler mappings. If no r->handler
has been set, but a content-type has, the content-type is copied to
r->handler.
Is there a use case for this? It makes it hard for handlers to check
if someone else h
