On 06/05/2012 21:20, Nikolaj wrote:
I would think you should look at your apache conf. First the request will go through Apache, which has to decide which handler will get the request.


Ummm... thanks but there's a bigger problem here - as I recall, Apache still serves the *.html, *.jpg etc from the sites whereas quercus handles the *.php. So how does apache know example.com/foo.jpg is actually on the disk under /www/quercus/example.com/foo.jpg unless it's aware of the resin config?

This is how httpd.conf looks:
LoadModule caucho_module /usr/lib/apache2/modules/mod_caucho.so

ResinConfigServer localhost 6800
CauchoConfigCacheDirectory /tmp
CauchoStatus yes

I have to comment all those out in order to get the sites served by regular php.



On Sat, May 5, 2012 at 10:34 PM, Stargazer <starga...@blueyonder.co.uk <mailto:starga...@blueyonder.co.uk>> wrote:

    I just installed resin to a server with > 100 php apps (your
    typical mix
    of drupal etc) intending for just a few to use Quercus as a test, then
    move the rest over in a managed way. What I find is all sites now fail
    as resin as hijacked the *.php extension. Its pretty much a default
    installation, all I did was attempt to fix this with commenting
    out the
    *.php servlet-mapping in app-default.xml but it had no effect.
    What have
    I missed please?

    _______________________________________________
    resin-interest mailing list
    resin-interest@caucho.com <mailto:resin-interest@caucho.com>
    http://maillist.caucho.com/mailman/listinfo/resin-interest




_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to