Hopbot log for 2009-08-19 - Helma IRC channel: #helma on irc.freenode.net

2009-08-19:

[16:14] <Flogge> hey
[16:14] <Flogge> does anyone know how to use mod_proxy_ajp (the successor of mod_jk it seems) with Helma?
[16:27] <earl> Flogge: sure, any specifics you need?
[16:27] <Flogge> hm?
[16:27] <Flogge> not really... I am using antville
[16:27] <Flogge> thats it :-D
[16:27] <earl> so just the general setup of ajp?
[16:28] <Flogge> yup, basically
[16:28] <earl> i'm usually using mod_rewrite, because i'm accustomed to it
[16:29] <Flogge> sounds good to me
[16:29] <earl> RewriteRule ^/(.*)$ ajp://127.0.0.1:8010/shnitzl-production%{REQUEST_URI} [P
[16:29] <Flogge> ah
[16:29] <earl> hm, got truncated
[16:29] <Flogge> and how do I enable AJP in HOP?
[16:30] <Flogge> or do I simply start it
[16:30] <Flogge> oh, by the way
[16:30] <Flogge> I have one specific
[16:30] <earl> just pass -jk along with a listen addr at the commandline
[16:30] <Flogge> I want to inject custom HTTP-headers for Shibboleth
[16:31] <earl> e.g. -jk 127.0.0.1:8010
[16:31] <Flogge> ah ok
[16:32] <earl> if you're using the linux init scripts that come along with helma, change HELMA_ARGS in the helma.conf config file
[16:33] <earl> i've no idea re shibboleth
[16:33] <Flogge> earl: I use Shibboleth as a module
[16:33] <Flogge> it catches certain URIs
[16:33] <Flogge> does its single sign on magic
[16:33] <earl> apache module?
[16:33] <Flogge> and returns custom HTTP headers to the script
[16:33] <Flogge> yup+
[16:33] <earl> ah, ok
[16:34] <Flogge> so I must be able to read them
[16:34] <earl> well, no idea how that interacts with proxied requests
[16:34] <Flogge> "regular proxying" would mess with them
[16:34] <Flogge> so I hope ajp will get it right
[16:34] <Flogge> :_D
[16:34] <Flogge> :-D
[16:34] <earl> i think that's mostly a matter of 'phase ordering'
[16:35] <earl> as long as the shibboleth stuff is done before the request gets passed to the proxy module, the headers _should_ just be passed on to helma
[16:37] <Flogge> bugger, my start.sh doesn't care about the settings in helma.conf
[16:37] <Flogge> earl: I hope so too. :-)
[16:38] <earl> in start.sh, just uncomment the AJP13_PORT line
[16:38] <Flogge> yup
[16:38] <Flogge> I did that
[16:38] <earl> then helma should be listening on port 8009 for ajp requests
[16:39] <earl> you can do a quick 'netstat -ltn' to confirm
[16:41] <Flogge> so I won't need module_proxy_ajp?
[16:41] <Flogge> uhm module_ajp_proxy
[16:42] <earl> you need two things: apache talking via ajp, that is done with mod_proxy_ajp
[16:43] <earl> and you need helma listening for ajp requests
[16:43] <Flogge> helma is listening
[16:43] <Flogge> and the module is loaded
[16:44] <earl> good
[16:44] <earl> then you'll need to configure apache to forward some requests via ajp to helma
[16:49] <Flogge> damn, my apache is choking on the Header command
[16:49] <Flogge> although I have included headers_module
[16:51] <earl> what happens?
[16:52] <Flogge> it doesn't load the modules
[16:56] <Flogge> ah
[16:56] <Flogge> I should READ before I play around
[16:57] <Flogge> # Files in this directory are created at apache start time by /usr/sbin/rcapache2
[16:57] <Flogge> # Do not edit them!
[16:57] <Flogge> :-D
[16:57] <earl> hehe
[17:00] <Flogge> grrr
[17:00] <Flogge> now the config is OK
[17:00] <Flogge> but I get Starting httpd2 (prefork) startproc: exit status of parent of /usr/sbin/httpd2-prefork: 1
[17:04] <Flogge> I give up
[17:04] <Flogge> thanks anyway
[17:04] <Flogge> :-D

 

 

In the channel now:

Logs by date: