----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Friday, March 08, 2002 11:40 AM
Subject: Re: cvs commit:
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote Request.java


>
>
> On Fri, 8 Mar 2002, Remy Maucherat wrote:
>
> > Date: Fri, 8 Mar 2002 11:20:57 -0800
> > From: Remy Maucherat <[EMAIL PROTECTED]>
> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> > To: Tomcat Developers List <[EMAIL PROTECTED]>
> > Subject: Re: cvs commit:
> >     jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote
Request.java
> >
> > > I've just started the 3.3.x port of Coyote.  I can manage to set this
one,
> > > but who uses it?  The Processor (currently) doesn't look at it
(AFAIK).
> >
> > That's the problem at the moment. I'm still undecided as to what goes
where.
> > The 'secure' flag may be Catalina specific (and the processor has no
clue
> > whether or not the connection is secure; it's the connector which knows
> > that), so I moving it to the adapter.
> >
I was just asking. :)  3.3.x has the flag as well, since isSecure() is also
in 2.2.  It's just that I wasn't planning on exposing the o.a.c.Request to
the rest of Tomcat so if nobody was ever going to look at the flag, I could
ignore it.
>
> Catalina uses the "secure" property of the current HTTP connector to give
> the right answer to ServletRequest.isSecure().  I imagine the same thing
> will need to be done for Coyote (and the "secure" flag would also need to
> be sent along for a JK request because it can vary each time???).
>
> > The API may change a bit. Maybe it will become closer to the one used by
TC
> > 3.3. I hope you don't mind the API stability problems too much ...
> > Hopefully, it will be stable soon.
> >
I don't mind at all. :)
> > Remy
> >
>
> Craig
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to