Mailing List Archive: Cherokee: users

Inline PHP

Index | Next | Previous | View Threaded

dmiller at amfes

Nov 2, 2009, 1:40 PM

Post #1 of 6 (641 views)
Permalink

Inline PHP

Assuming PHP is otherwise working for a "standard" configuration, is
enabling inline php support just a matter of editing the
application/x-httpd-php mime type and adding "html" to the extension list?

If so...I'll ask the next question on behalf of somebody else since I
don't THINK I'll need it...

Can mime types be specified on a per-virtual server basis? Or only
system-wide?
--
Daniel

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

alvaro at octality

Nov 2, 2009, 5:05 PM

Post #2 of 6 (609 views)
Permalink

Re: Inline PHP [In reply to]

On 02/11/2009, at 15:40, Daniel L. Miller wrote:

> Assuming PHP is otherwise working for a "standard" configuration, is
> enabling inline php support just a matter of editing the
> application/x-httpd-php mime type and adding "html" to the extension
> list?

No. You'd have to edit the "Extension PHP" rule and replace: "php" by
"php,html".

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

dmiller at amfes

Nov 3, 2009, 1:25 PM

Post #3 of 6 (600 views)
Permalink

Re: Inline PHP [In reply to]

Alvaro Lopez Ortega wrote:
> On 02/11/2009, at 15:40, Daniel L. Miller wrote:
>
>> Assuming PHP is otherwise working for a "standard" configuration, is
>> enabling inline php support just a matter of editing the
>> application/x-httpd-php mime type and adding "html" to the extension
>> list?
>
> No. You'd have to edit the "Extension PHP" rule and replace: "php" by
> "php,html".
Ok - does that mean ONLY modify the extension rule? Or do both the mime
and extension changes?

--
Daniel
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

alvaro at octality

Nov 3, 2009, 1:34 PM

Post #4 of 6 (601 views)
Permalink

Re: Inline PHP [In reply to]

On 03/11/2009, at 15:25, Daniel L. Miller wrote:
Alvaro Lopez Ortega wrote:
>> On 02/11/2009, at 15:40, Daniel L. Miller wrote:
>>
>>> Assuming PHP is otherwise working for a "standard" configuration, is
>>> enabling inline php support just a matter of editing the
>>> application/x-httpd-php mime type and adding "html" to the extension
>>> list?
>>
>> No. You'd have to edit the "Extension PHP" rule and replace: "php" by
>> "php,html".
> Ok - does that mean ONLY modify the extension rule? Or do both the
> mime
> and extension changes?

Only the rule.

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

stefan at konink

Nov 3, 2009, 1:37 PM

Post #5 of 6 (624 views)
Permalink

Re: Inline PHP [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Daniel L. Miller schreef:
> Alvaro Lopez Ortega wrote:
>> On 02/11/2009, at 15:40, Daniel L. Miller wrote:
>>
>>> Assuming PHP is otherwise working for a "standard" configuration, is
>>> enabling inline php support just a matter of editing the
>>> application/x-httpd-php mime type and adding "html" to the extension
>>> list?
>> No. You'd have to edit the "Extension PHP" rule and replace: "php" by
>> "php,html".
> Ok - does that mean ONLY modify the extension rule? Or do both the mime
> and extension changes?

Only the extension rule :)

Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREKAAYFAkrwon8ACgkQYH1+F2Rqwn2yigCbB3rx4rG+HUcBaEsRaNbr4Ow7
DXYAnAuvtb8cIWbi6hzJHA1j4B6pcxnP
=reY3
-----END PGP SIGNATURE-----
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

gwolf at gwolf

Nov 4, 2009, 5:24 AM

Post #6 of 6 (606 views)
Permalink

Re: Inline PHP [In reply to]

Daniel L. Miller dijo [Tue, Nov 03, 2009 at 01:25:23PM -0800]:
> >> Assuming PHP is otherwise working for a "standard" configuration, is
> >> enabling inline php support just a matter of editing the
> >> application/x-httpd-php mime type and adding "html" to the extension
> >> list?
> >
> > No. You'd have to edit the "Extension PHP" rule and replace: "php" by
> > "php,html".
> Ok - does that mean ONLY modify the extension rule? Or do both the mime
> and extension changes?

AFAICT, when you are defining the PHP extension, you are effectively
overriding whatetver MIME type would be sent - The MIME type for
PHP-generated content is no longer any of the application/x-httpd-php
derivatives, but whatever the script states (usually, text/html).

If I understand correctly, the declared MIME types are only sent for
the 'file' handler.

--
Gunnar Wolf • gwolf [at] gwolf • (+52-55)5623-0154 / 1451-2244
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads