If it doesn't by default, it's not difficult to hack the Apache
response chain and make it do whatever you want. Still, it's probably
easier just to have a working copy. Alternatively, you could also just
have a PHP script that fetches files from the repo and does any
necessary processing.
On 6/29/06, Rainer Sokoll <r.sokoll@intershop.de> wrote:
> Greg Thomas wrote:
> > On Thu, 29 Jun 2006 15:23:51 +0200, Rainer Sokoll
> > <r.sokoll@intershop.de> wrote:
>
> >>What if svn:mime-type is set to application/x-httpd-php?
> >
> > The MIME type of a file only affects how the client displays it. PHP
> > etc. code is processed server side.
>
> [The discussion goes slightly off topic, but I cannot stop myself ;-)]
>
> I disagree.
> To my best knowledge:
> If you do not have somewhere in your apache config:
>
> "AddType application/x-httpd-php .php" or
> "application/x-httpd-php php" in mime.types
>
> then apache will deliver the contents of your php file as text/plain.
> If you have one of the statements above, apache will pass the php file
> to mod_php (if DSO is supported) and then deliver whatever the php
> script returns.
> So my question is: Does mod_svn give back its results to apache for
> further processing (for example mod_php) or not?
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 29 17:44:43 2006