> Just a couple of things to add:
>
> 1. I suspect, but don't know for sure, that isSecure() (and
>getScheme()) should work correctly even with forwards/redirects as
>well. Of course, if you found that isSecure() doesn't work with
>basic https, as apparently is the case above, the pro
On Thu, 7 Nov 2002, Chris Parker wrote:
> > This came up a week or so ago. Check here for a very
> > comprehensive reply from Milt Epstein. In short, isSecure is
> > exactly the method you should use, and it does know if the
> > original request is SSL or not. If it is always returning
> > 'fal
> This came up a week or so ago. Check here for a very comprehensive reply
> from Milt Epstein. In short, isSecure is exactly the method you should
use,
> and it does know if the original request is SSL or not. If it is always
> returning 'false', something else is going on.
>
> http://marc.thea
on.
http://marc.theaimsgroup.com/?l=tomcat-user&m=103608496529118&w=2
John
> -Original Message-
> From: Chris Parker [mailto:cparker@;cya.ca.gov]
> Sent: Thursday, November 07, 2002 12:21 PM
> To: Tomcat Users List
> Subject: Re: Tomcat-Apache SSL - Extension Question
>
>
&
[reply]
> You need to understand the difference between running Tomcat
> standalone and integrated with a web server (such as Apache).
..
[snip]
[/reply]
Knowing all this, is there a way for a servlet to reliably know whether
Apache is currently replying to http or https? The Apache connector por