[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: upgrade to subversion 1.8.5 suspected bug

From: Austin Mico <un.f.m.o.j_at_gmail.com>
Date: Wed, 22 Jan 2014 13:43:39 +0800

Here is the php conf:

#
# PHP is an HTML-embedded scripting language which attempts to make it
# easy for developers to write dynamically generated webpages.
#

<IfModule prefork.c>
  LoadModule php5_module modules/libphp5.so
</IfModule>
<IfModule worker.c>
  LoadModule php5_module modules/libphp5-zts.so
</IfModule>

#
# Cause the PHP interpreter to handle files with a .php extension.
#
AddHandler php5-script .php
AddType text/html .php

#
# Add index.php to the list of files that will be served as directory
# indexes.
#
DirectoryIndex index.php

#
# Uncomment the following line to allow PHP to pretty-print .phps
# files as PHP source code:
#
#AddType application/x-httpd-php-source .phps

Thanks

On Wed, Jan 22, 2014 at 11:15 AM, Nico Kadel-Garcia <nkadel_at_gmail.com>wrote:

> On Tue, Jan 21, 2014 at 8:38 PM, Ben Reser <ben_at_reser.org> wrote:
>
> > This is a side effect of the change to setting the filename entry in the
> > request record with 1.8.5. See the 2nd yellow box here:
> >
> http://subversion.apache.org/docs/release-notes/1.8.html#mod_dav_svn-fsmap
> >
> > I'd guess you have some sort of handler or filter that's messing with
> php files.
> >
> > So post your full httpd conf and I can probably point you at what you
> have
> > configured wrong.
>
>
> Given that he saw this error mesage:
>
>
> Starting httpd: (98)Address already in use: make_sock: could not
> bind to address 0.0.0.0:80
> no listening sockets available, shutting down
>
> I'm going to be *really surprised* if something involving a syntax
> change for handling local files, or Subversion directory paths, would
> cause that error. This looks like something else is already on port
> 80.
>
Received on 2014-01-22 06:44:17 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.