On Mon, Aug 01, 2005 at 04:02:05PM -0400, Dan Mahoney, System Admin wrote:
> You need to get the frontpage support from rtr.com, and extract it the the
> (very universal) /usr/local/frontpage.
>
> From there, to make it play nice with apache, you can compile and build
> mirfak.
>
> Doing it the "pure" rtr way requires patching your httpd source and/or
> compiling a static module. Bad juju.
>
> Additionally, Mirfak gives you the cool ability to add apache
> configuration commands per-vhost enabling or disabling the frontpage
> support, so it's not "out there" for people to mess with in the event a
> hole is found.
>
> I've got this all running well.
Cheers. I've moved over to the mirfak mod_frontpage, but still get the same
error now:
0x0020: .... .... .... .... 4854 5450 2f31 2e31 P...S...HTTP/1.1
0x0030: 2034 3031 200d 0a44 6174 653a 2054 7565 .401...Date:.Tue
...
0x0150: 416c 6976 650d 0a54 7261 6e73 6665 722d Alive..Transfer-
0x0160: 456e 636f 6469 6e67 3a20 6368 756e 6b65 Encoding:.chunke
0x0170: 640d 0a0d 0a64 3820 0d0a 3c68 746d 6c3e d....d8...<html>
0x0180: 3c68 6561 643e 3c74 6974 6c65 3e76 6572 <head><title>ver
0x0190: 6d65 6572 2052 5043 2070 6163 6b65 743c meer.RPC.packet<
0x01a0: 2f74 6974 6c65 3e3c 2f68 6561 643e 0a3c /title></head>.<
0x01b0: 626f 6479 3e0a 3c70 3e6d 6574 686f 643d body>.<p>method=
0x01c0: 6c69 7374 2073 6572 7669 6365 733a 332e list.services:3.
0x01d0: 302e 322e 300a 3c70 3e73 7461 7475 733d 0.2.0.<p>status=
0x01e0: 0a3c 756c 3e0a 3c6c 693e 7374 6174 7573 .<ul>.<li>status
0x01f0: 3d33 3237 3638 340a 3c6c 693e 6f73 7374 =327684.<li>osst
0x0200: 6174 7573 3d30 0a3c 6c69 3e6d 7367 3d54 atus=0.<li>msg=T
0x0210: 6865 7265 2069 7320 6e6f 2077 6562 206e here.is.no.web.n
0x0220: 616d 6564 2026 2333 343b 2623 3334 3b2e amed."".
0x0230: 0a3c 6c69 3e6f 736d 7367 3d0a 3c2f 756c .<li>osmsg=.</ul
0x0240: 3e0a 3c2f 626f 6479 3e0a 3c2f 6874 6d6c >.</body>.</html
0x0250: 3e0a 0d0a >...
Possibly this is due to how I installed the frontpage extensions into the
website. I haven't found a good document on this, and I'm not running
install_fp.sh; apart from not trusting this script to run as root, I'm doing
all this inside a chroot environment where apxs doesn't exist.
What I'm actually doing is (inside the chroot):
# /usr/local/frontpage/version5.0/bin/owsadm.exe -o install -p 80 \
-m www.example.com -u fpadmin -pw fppass -t apache-fp -s /conf/fp.conf \
-xu test -xg test
Starting install, port: 80.
Creating web http://www.example.com.
Chowning Content in service /.
Install completed.
Where /conf/fp.conf contains:
# cat /conf/fp.conf
Port 80
ServerRoot "/usr/local"
ResourceConfig /dev/null
AccessConfig /dev/null
DocumentRoot /web/sites
<VirtualHost www.example.com>
DocumentRoot /web/sites/e/x/a/example.com/public/www
</VirtualHost>
This gives:
# cd /web/sites/e/x/a/example.com/public/www
# ls -l
total 22
-rw-r--r-- 1 test test 393 Aug 2 09:21 .htaccess
drwx------ 2 test test 512 Aug 2 09:21 _private
drwxr-xr-x 4 test test 512 Aug 2 09:21 _vti_bin
drwxr-xr-x 2 test test 512 Aug 2 09:21 _vti_cnf
-rw-r--r-- 1 test test 1754 Aug 2 09:21 _vti_inf.html
drwxr-xr-x 2 test test 512 Aug 2 09:21 _vti_log
drwxr-xr-x 2 test test 512 Aug 2 09:21 _vti_pvt
drwxr-xr-x 2 test test 512 Aug 2 09:21 _vti_txt
drwxr-xr-x 2 test test 512 Aug 2 09:21 images
-rw-r--r-- 1 test test 2448 Aug 2 09:21 postinfo.html
# cat _vti_bin/.htaccess
# -FrontPage-
Options None
<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName bloodhound.noc.clara.net
AuthUserFile /web/sites/e/x/a/example.com/public/www/_vti_pvt/service.pwd
AuthGroupFile /web/sites/e/x/a/example.com/public/www/_vti_pvt/service.grp
(I note there's no "Require valid-user" or "AuthType Basic" in there, so
it's not Apache which is enforcing access restrictions; it must be down to
the frontpage system)
# cat /web/sites/e/x/a/example.com/public/www/_vti_pvt/service.pwd
# -FrontPage-
fpadmin:LCqM/xFk79dtI
This looks OK.
# cat /web/sites/e/x/a/example.com/public/www/_vti_pvt/service.grp
# -FrontPage-
administrators: fpadmin
authors:
Hmm. Tried setting 'authors: fpadmin' manually, but that didn't change
things.
# cat /usr/local/frontpage/www.example.com:80.cnf
vti_encoding:SR|utf8-nl
servertype:apache-fp
authoring:enabled
extenderversion:5.0.2.2634
frontpageroot:/usr/local/frontpage/version5.0
serverconfig:/conf/fp.conf
Perhaps the piece I'm missing is I don't understand what fp_install means by
a "root web" versus a "subweb" versus a "virtualweb". Have you got any
pointers to this? Does it actually need something to be installed other than
what goes into the VirtualHost document root?
Looks like my next step will be to make a *full* chroot environment,
completely with sources, fire up install_fp.sh and see if I can get it to
work that way.
Regards,
Brian.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
