tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milt Epstein <>
Subject Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3 Connector
Date Fri, 01 Nov 2002 15:50:45 GMT
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)

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message