Hi, Le samedi 12 janvier 2008 12:41:02, go...@oles.biz a écrit : > Package: libapache2-mod-jk > Version: 1:1.2.25-2 > Severity: normal > > Apache http server do not forward requests to tomcat and failed with error > "The requested URL /..../ was not found on this server". It's very strange > behavior for me. Does libapache2-mod-jk 1.2.26-1 requires different > configuration from 1.2.25-2 ? > > It's my configuration: > > NameVirtualHost *:80 > NameVirtualHost *:443 > > JkWorkersFile /etc/libapache2-mod-jk/workers.properties > JkOptions +ForwardKeySize +ForwardURICompat > JkMount /dir1/* ajp13_worker > JkMount /dir2/* ajp13_worker > > <VirtualHost> > </VirtualHost> > .............
I'm trying to cleanup issues in libapache2-mod-jk package and this issue popped up on my radar :) I can confirm that there was a change/fix in upstream handling of JkMount "copy" from global scope to VirtualHost in 1.2.26. From upstream changelog [1], there was a SVN revision [2] that "add new value "All" for JkMountCopy directive and this will switch the default of JkMountCopy from Off to On for all virtual servers." So previously (< 1.2.25) having a JkMount directive inside your global scope should have copied this to every child virtualhost. 1.2.26 fixed this issue and now provide a way to enable your expected behavior : - set JkMountCopy All in you global scope - set JkMountCopy On in each VirtualHost where you want to enable global scope JkMount I'll had some warning/docs regarding this into libapache2-mod-jk in unstable. [1] http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html [2] http://svn.apache.org/viewvc?view=revision&revision=580809 Cheers, -- Damien - Debian Developper http://wiki.debian.org/DamienRaudeMorvan
signature.asc
Description: This is a digitally signed message part.
