I've seen a few threads about this, but I haven't seen anyone actually
produce one, so as far as I'm aware there isn't currently a way to use
Jetty as a frontend HTTP server, transparently proxying requests from
regular HTTP clients on to another HTTP server behind the scenes
("reverse proxy" as Apache's mod_proxy calls it).
client] --request--> Jetty [auth] --request--> [$other HTTP server]
The work on the Jetty HTTP client is encouraging, but I've got an urgent
(read: by tomorrow!) need for a HTTP proxy handler which can hook into
JAAS, so it looks like I might be up for a night of 'fun' as I try to
build the proxy handler/servlet I need!
If I actually get anywhere with this, I will of course post the code
(although it may not be pretty - if I need to do a gross hack or 50 just
to get it working, I will).
If it works, then it's going to be bye-bye Apache and bye-bye AJP13
(thanks for the hard work, bong!) for us, I think.
I've also had some success with getting the Citrix Web Interface running
under Jetty (in case anyone's interested). The remaining problems with
that are Citrix-related, rather than anything to do with Jetty.
Russell Howe, IT Manager. <rhowe@...>
BMT Marine & Offshore Surveys Ltd.