You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Milt Epstein <me...@uiuc.edu> on 2002/11/01 16:50:45 UTC
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3 Connector
On Fri, 1 Nov 2002, Steinar Bang wrote:
> Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3
> tomcat 4.1.12, BlackDown Java SDK 1.3.1,
> Struts 1.1-b2
>
> Is there a way to pass the scheme used by the client when talking to
> the apache server (ie. "http" or "https") through the Coyote AJP 1.3
> connector?
>
> If I use the old AJP 1.3 connector, I can use the
> HttpServletRequest.isSecure() function to determine if the client used
> an HTTPS connection to the apache server.
>
> With the Coyote AJP 1.3 connector this information is lost.
> Ie. HttpServletRequest.isSecure() always returns false, and
> HttpServletRequest.getScheme() always returns "http".
>
> The <Connector> elelement for Coyote have the attributes secure, and
> scheme, which affects the above values of HttpServletRequest. But
> these settings are constants.
>
> Do I need to set up a separate AJP 1.3 connection on a different port
> to handle HTTPS requests to apache? If so, how's that done?
Search the archives, this has come up twice in the last few weeks. It
may be that there's a bug with the Coyote AJP13 connector.
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tomcat version numbering (Was: HttpServletRequest.isSecure()
fails...)
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Wed, 20 Nov 2002, Steinar Bang wrote:
>
> If one looks at the distribution directory of tomcat, it is easy to
> get confused. It contains the directories:
> v4.0.5/ 09-Oct-2002 07:28 -
> v4.0.6/ 08-Oct-2002 08:27 -
> v4.1.12/ 02-Oct-2002 03:01 -
> v4.1.15-alpha/ 14-Nov-2002 00:48 -
>
> Ie. there's a 4.1.12, no 4.1.13, or 4.1.14, but instead a 4.1.15 that
> is marked alpha. The immediate question is: is this an alpha of a
> final 4.1.15 release? Or is 4.1.15 an alpha release of the final
> version of 4.1.x?
>
> A bit of googling found me
> <URL:http://www.faqchest.com/prgm/tomcat-l/tmct-02/tmct-0208/tmct-020879/tmct02082620_30399.html >
>
> And I guess the answer is sort of the first one, and sort of the last
> one. Ie. if 4.1.15-alpha turns out to be a stable release, the
> "-alpha" will be yanked from the version number, and 4.1.15 will
> become a production release.
>
Yep.
> However, if 4.1.15 isn't found good enough, it will be completely
> yanked from the distribution directory, and consigned to the scrapheap
> of history. And then a new version 4.1.16-alpha will be announced.
>
> I'm still a little confused, but I guess that whatever 4.1.x with
> x>=14 is finally released, will have a working
> HttpServletRequest.isSecure() when using the Coyote Ajp1.3 connector.
>
Tomcat 4.1 is following the same basic release policy that the Apache
HTTPD server, and several other Jakarta projects, are using. Milestone
releases happen regularly, and go out with a default state of "alpha".
After some evaluation time, the milestones might get voted (by the
committers, based on user feedback) as "beta" or "general release"
quality. There is not any such thing as the "final" release of 4.1.x
(until people stop working on it, which would only happen if a subsequent
4.2.x or 5.0.x release was pretty solid) -- only the latest production
release, which is currently 4.1.12.
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
tomcat version numbering (Was: HttpServletRequest.isSecure()
fails...)
Posted by Steinar Bang <sb...@dod.no>.
>>>>> Steinar Bang <sb...@dod.no>:
>>>>> Steinar Bang <sb...@dod.no>:
>> Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate
>> branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD?
> Not sure if they are branch tags, but there are tags named
> TOMCAT_4_1_13 and TOMCAT_4_1_14.
If one looks at the distribution directory of tomcat, it is easy to
get confused. It contains the directories:
v4.0.5/ 09-Oct-2002 07:28 -
v4.0.6/ 08-Oct-2002 08:27 -
v4.1.12/ 02-Oct-2002 03:01 -
v4.1.15-alpha/ 14-Nov-2002 00:48 -
Ie. there's a 4.1.12, no 4.1.13, or 4.1.14, but instead a 4.1.15 that
is marked alpha. The immediate question is: is this an alpha of a
final 4.1.15 release? Or is 4.1.15 an alpha release of the final
version of 4.1.x?
A bit of googling found me
<URL:http://www.faqchest.com/prgm/tomcat-l/tmct-02/tmct-0208/tmct-020879/tmct02082620_30399.html >
And I guess the answer is sort of the first one, and sort of the last
one. Ie. if 4.1.15-alpha turns out to be a stable release, the
"-alpha" will be yanked from the version number, and 4.1.15 will
become a production release.
However, if 4.1.15 isn't found good enough, it will be completely
yanked from the distribution directory, and consigned to the scrapheap
of history. And then a new version 4.1.16-alpha will be announced.
I'm still a little confused, but I guess that whatever 4.1.x with
x>=14 is finally released, will have a working
HttpServletRequest.isSecure() when using the Coyote Ajp1.3 connector.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3
Connector
Posted by Steinar Bang <sb...@dod.no>.
>>>>> Steinar Bang <sb...@dod.no>:
> Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate
> branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD?
Not sure if they are branch tags, but there are tags named
TOMCAT_4_1_13 and TOMCAT_4_1_14.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3
Connector
Posted by Steinar Bang <sb...@dod.no>.
>>>>> "Bill Barker" <wb...@wilshire.com>:
>> On Fri, 1 Nov 2002, Steinar Bang wrote:
>>> If I use the old AJP 1.3 connector, I can use the
>>> HttpServletRequest.isSecure() function to determine if the client
>>> used an HTTPS connection to the apache server.
>>> With the Coyote AJP 1.3 connector this information is lost.
>>> Ie. HttpServletRequest.isSecure() always returns false, and
>>> HttpServletRequest.getScheme() always returns "http".
> I believe that this is a bug, and has been fixed in 4.1.14 (and,
> even, 4.1.13 if you can run Tomcat without a sandbox).
Thanx for the info! As far as I can tell, 4.1.12 is the latest
available version of tomcat, even counting nightly builds?
Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate
branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD?
Thanx!
- Steinar
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3 Connector
Posted by Bill Barker <wb...@wilshire.com>.
"Milt Epstein" <me...@uiuc.edu> wrote in message
news:Pine.GSO.4.31.0211010950030.27414-100000@staff2.cso.uiuc.edu...
> On Fri, 1 Nov 2002, Steinar Bang wrote:
>
> > Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3
> > tomcat 4.1.12, BlackDown Java SDK 1.3.1,
> > Struts 1.1-b2
> >
> > Is there a way to pass the scheme used by the client when talking to
> > the apache server (ie. "http" or "https") through the Coyote AJP 1.3
> > connector?
> >
> > If I use the old AJP 1.3 connector, I can use the
> > HttpServletRequest.isSecure() function to determine if the client used
> > an HTTPS connection to the apache server.
> >
> > With the Coyote AJP 1.3 connector this information is lost.
> > Ie. HttpServletRequest.isSecure() always returns false, and
> > HttpServletRequest.getScheme() always returns "http".
> >
> > The <Connector> elelement for Coyote have the attributes secure, and
> > scheme, which affects the above values of HttpServletRequest. But
> > these settings are constants.
> >
> > Do I need to set up a separate AJP 1.3 connection on a different port
> > to handle HTTPS requests to apache? If so, how's that done?
>
> Search the archives, this has come up twice in the last few weeks. It
> may be that there's a bug with the Coyote AJP13 connector.
I believe that this is a bug, and has been fixed in 4.1.14 (and, even,
4.1.13 if you can run Tomcat without a sandbox).
>
> Milt Epstein
> Research Programmer
> Integration and Software Engineering (ISE)
> Campus Information Technologies and Educational Services (CITES)
> University of Illinois at Urbana-Champaign (UIUC)
> mepstein@uiuc.edu
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>