Re: problem: Debian apache2 + php4-cgi + attachments

On Jan 06, 2004, at 10:46, Moritz Bunkus wrote:

>> I think what you might want to do is use apache 1.3.
>
> Not really, for one I like apache2, and the (more important reason) is
> that I have SVN repositories on those servers as well which do require
> Apache2 because they're working via WebDAV. I would definitely not want
> to have a dual-apache setup.

Hmmm... yeah, I hear ya on that.

>> After having a few discussions with people, apache2+php is not really
>> a good match.
>
> That's probably why the Debian folks haven't built such packages
> themselves.

Could be.

>> Some really big PHP apps just don't work properly.  Thankfully, 
>> Anthill
>> does for the most part.
>
> Do you have some more information / URLs on this topic? Is 'only' PHP4
> having such difficulties with Apache2 and will PHP5 work better? Or is
> this a fundamental problem? Apache+PHP is such a widely used 
> combination
> that I doubt that the developpers aren't working hard to get PHP and
> Apache2 working together.

I don't, this is discussing with some other PHP developers and the 
Mandrake apache maintainer.  From my understanding, the PHP folks are 
blaming the Apache folks and vice versa.  I don't think PHP5 changes 
anything because it's how Apache and PHP talk to each other (ie. PHP 
and Apache 1.3 don't have this problem).

>> If that isn't an option, I'm not sure what you can attempt to do short
>> of compiling PHP for apache2 yourself.
>
> I'll probably do that and see what happens :)

I've not had any problem using Anthill with apache2+PHP... from my 
understanding, it's heavy math and hashes where the problems crop up 
for the most part.

>> I don't really want to change how the attachments are handled because
>> I think this way is "smart".
>
> Understandable, and thanks for the explanation. If nothing else works
> I'll modify the attachment handling locally to use ? style
> parameters. Or maybe even Apache's rewrite engine could be
> used... Hmm... I don't know much about it, but maybe I'll look into 
> that
> as well.

I'd try building PHP from source instead.  That might be the easiest 
solution.

---
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD}

_______________________________________________
Anthill-workers mailing list
Anthill-workers-+mQDA36h6dWw5LPnMra/[email protected]
http://vmlinuz.ca/mailman/listinfo/anthill-workers