-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 11/17/2009 11:59 AM, David Smith wrote:
> Christopher Schultz wrote:
>> David,
>>
>> On 11/17/2009 7:39 AM, David Smith wrote:
>>> Your tomcat has to listen on 443 to remove the port number from the
>>> URL. This is not a tomcat issue, but
Christopher Schultz wrote:
> David,
>
> On 11/17/2009 7:39 AM, David Smith wrote:
> > Your tomcat has to listen on 443 to remove the port number from the
> > URL. This is not a tomcat issue, but rather the browser's expectation.
>
> That's not entirely true. If Robert configures his firewall to re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 11/17/2009 7:39 AM, David Smith wrote:
> Your tomcat has to listen on 443 to remove the port number from the
> URL. This is not a tomcat issue, but rather the browser's expectation.
That's not entirely true. If Robert configures his firewa
That's exactly what I was hoping for, thanks David (and others who have
posted), you're a gent.
I thought it might be something like that but I couldn't find any conclusive
evidence about handling secure ports...
R.
On 17 Nov 2009, at 12:39, David Smith wrote:
> Your tomcat has to listen on
> It works fine but as it stands https requests have the form
> https://mydomain.com:8443. I would like to set it up so like
> most secure internet sites there is no port number in the URL
> even when using https. Can anyone point me in the right
> direction or at some documentation that will h
Am Tue, 17 Nov 2009 09:40:46 +
schrieb Robert Denison :
> I've set up my tomcat server to serve http requests on port 8080 and
> https on port 8443. My firewall forwards requests for 80 to 8080 and
> 8443 to 8443.
Tomcat cannot help you in this case.
You will have to make your firewall for
Your tomcat has to listen on 443 to remove the port number from the
URL. This is not a tomcat issue, but rather the browser's expectation.
-- David
On Nov 17, 2009, at 4:40 AM, Robert Denison wrote:
Hi,
I've set up my tomcat server to serve http requests on port 8080 and
https on port
