> > I agree with Remy the jetty-specific docs should go with jetty.
>
> Fair enough. Perhaps a pointer to where to find these docs might not
> go amiss, though?
We could add an URL in documentation to jetty HOW-TO.
> > For the native code - I think we can add specific instructions or
> > dire
On Mon, Jul 08, 2002 at 09:28:50AM -0700, [EMAIL PROTECTED] wrote:
> On Thu, 4 Jul 2002, Simon Stewart wrote:
>
> > > >Attached is a HOWTO on getting Jetty and Apache 2 talking via
> > > >mod_jk2. Can I please get some feedback on this? And what do people
> > > >think about this (or something sim
On Thu, 4 Jul 2002, Simon Stewart wrote:
> > >The Jetty folks have been working hard on improving the connectivity
> > >between apache and jetty and so from 4.1.D2 Jetty has shipped with its
> > >own AJP13 Listener. According to Greg Wilkins, the currently shipped
> > >version has problems with a
On Thu, Jul 04, 2002 at 03:57:37AM -0700, Remy Maucherat wrote:
> Simon Stewart wrote:
> >The Jetty folks have been working hard on improving the connectivity
> >between apache and jetty and so from 4.1.D2 Jetty has shipped with its
> >own AJP13 Listener. According to Greg Wilkins, the currently s
Simon Stewart wrote:
> The Jetty folks have been working hard on improving the connectivity
> between apache and jetty and so from 4.1.D2 Jetty has shipped with its
> own AJP13 Listener. According to Greg Wilkins, the currently shipped
> version has problems with authenticated and SSL connections,
The Jetty folks have been working hard on improving the connectivity
between apache and jetty and so from 4.1.D2 Jetty has shipped with its
own AJP13 Listener. According to Greg Wilkins, the currently shipped
version has problems with authenticated and SSL connections, but these
are solved in the
