This is a feature of the protocol; there's nothing you can do about idiot users who type strange things into their browsers' address bars.
What you *can* do is run your services on the standard ports - 80 and 443 - so that your users don't have to type in port numbers. Is there any reason you're not using the standard ports for this application? - Peter On 25 March 2010 14:47, Hagenlocher-Wemssen, Andreas < andreas.hagenlocher-wems...@siemens.com> wrote: > Hi all, > > I got a peculiar problem on a apache tomcat 5.5 server: > > Several clients, which could use the wrong port for their protocol. > > On the server there is a http port on 8080, and a https port on 8443 as > default. > > Unfortunately, on the clients there are possibilities to combine the > protocol freely with a port, so It could be that they try to connect with > https to 8080 (which results in a timeout on the client, triggering a error > message), > > Or with http to 8443, which gets a rather unpleasant surprise, they get a > page, without an error message, with some cryptic characters: > > ________________________________ > > [1][1] > > I would like to get a error message back ... can anyone help me? > > > > Andreas Hagenlocher-Wemßen > >
