Having trouble getting apache to listen without the port number appended

When i access the server using http://www.hostname.com I get a 404
response when I access it using http://www.hostname.com:30101 I get a
200 ie page found response and it works fine and dandy. I ran an
iptrace ( a sniffer ) on the server hosting the pages and the header
of the packets hitting the box in both cases have the correct
destination port of 30101 so our networking hardware seems to be doing
it's job fine. The body of the packet is identical apart from the port
number appended to the url when I append it in the address bar of my
browser. We are using tomcat whatever that is ( I am totally new to
tomcat ).
I have had an equally experienced unix admin colleague look at my
iptraces and he agrees it looks like a tomcat issue and that the
network hardware is doing it's job.
So how do I convince tomcat to respond correctly when it is hit on the
correct port without having to append the port to the address.
Thanks in advance, i am stumped.
Regards
Bozodebris.

Re: Having trouble getting apache to listen without the port number appended

On Sep 6, 9:39 am, bozo wrote:
> When i access the server usinghttp://www.hostname.comI get a 404
> response when I access it usinghttp://www.hostname.com:30101I get a
> 200 ie page found response and it works fine and dandy. I ran an
> iptrace ( a sniffer ) on the server hosting the pages and the header
> of the packets hitting the box in both cases have the correct
> destination port of 30101 so our networking hardware seems to be doing
> it's job fine. The body of the packet is identical apart from the port
> number appended to the url when I append it in the address bar of my
> browser. We are using tomcat whatever that is ( I am totally new to
> tomcat ).
> I have had an equally experienced unix admin colleague look at my
> iptraces and he agrees it looks like a tomcat issue and that the
> network hardware is doing it's job.
> So how do I convince tomcat to respond correctly when it is hit on the
> correct port without having to append the port to the address.
> Thanks in advance, i am stumped.
> Regards
> Bozodebris.

So, what you're saying, you're saying tomcat isn't responding on port
80 (like you think it should), but it is responding on port 30101?

Mike

Re: Having trouble getting apache to listen without the port number appended

On Sep 6, 6:41 pm, Mike wrote:
> On Sep 6, 9:39 am, bozo wrote:
>
>
>
> > When i access the server usinghttp://www.hostname.comIget a 404
> > response when I access it usinghttp://www.hostname.com:30101Iget a
> > 200 ie page found response and it works fine and dandy. I ran an
> > iptrace ( a sniffer ) on the server hosting the pages and the header
> > of the packets hitting the box in both cases have the correct
> > destination port of 30101 so our networking hardware seems to be doing
> > it's job fine. The body of the packet is identical apart from the port
> > number appended to the url when I append it in the address bar of my
> > browser. We are using tomcat whatever that is ( I am totally new to
> > tomcat ).
> > I have had an equally experienced unix admin colleague look at my
> > iptraces and he agrees it looks like a tomcat issue and that the
> > network hardware is doing it's job.
> > So how do I convince tomcat to respond correctly when it is hit on the
> > correct port without having to append the port to the address.
> > Thanks in advance, i am stumped.
> > Regards
> > Bozodebris.
>
> So, what you're saying, you're saying tomcat isn't responding on port
> 80 (like you think it should), but it is responding on port 30101?
>
> Mike
An understandable question....
When I put
http://www.tomcatserver.com/
in my browsers address bar. my sniffer can see the packets coming
into the tomcat server on the correct port 30101 as they should be,
the headers have the right destination port on them as our network
hardware is doing what it is supposed to be doing. But tomcat gives
url not found 404.

When I put
http://www.tomcatserver.com:30101
in my browser address bar. I can see the packets coming into the
tomcat server on port 30101 as they should be, the headers have the
right destination port on them
But tomcat gives the correct response and responds with the data I
want....

What I want is to put
http://www.tomcatserver.com
into the address bar without the port, the packets should hit the
tomcat server on port 30101 and tomcat should give me the data NOT 404
url not found. It would be a major pain to change all the code that
accesses the tomcat server to add port 30101 to all requests to the
tomcat server, a change control and coding nightmare that would take a
long time.

Re: Having trouble getting apache to listen without the port number appended

Hi Bozo,
standard port for http: is 80. So you have to either ...

reconfigure your tomcatserver to listen to port 80,

.... or ...

put something like a nat (network adress translation) or port forwarding
between your network hardware and your tomcat server. Most isdn / dsl router
have functionality that does adress translation or port forwarding, many
firewall system can do this, most microsoft operating systems can do this,
most linux versions can do this.
Search your manuals for network adress translation and / or port forwarding
or ask your local administrator.

greetings from germany
Chris

Re: Having trouble getting apache to listen without the port number appended

On Sep 7, 10:04 am, Christian Stüben wrote:
> Hi Bozo,
> standard port for http: is 80. So you have to either ...
>
> reconfigure your tomcatserver to listen to port 80,
>
> ... or ...
>
> put something like a nat (network adress translation) or port forwarding
> between your network hardware and your tomcat server. Most isdn / dsl rou=
ter
> have functionality that does adress translation or port forwarding, many
> firewall system can do this, most microsoft operating systems can do this,
> most linux versions can do this.
> Search your manuals for network adress translation and / or port forwardi=
ng
> or ask your local administrator.
>
> greetings from germany
> Chris

The design is to use port 30101, this is not being used as a web
server in the normal sense. We do not want to use port 80. The network
hardware, natting, port forwarding etc is working fine. I have done a
trace on the packets and the destination port on them is being
assigned correctly as port 30101. Tomcat is misbehaving as far as I
and another senior unix admin can tell.

Re: Having trouble getting apache to listen without the port number appended

Hi Bozo,

"bozo" schrieb im Newsbeitrag
news:1189159458.838236.26560@r29g2000hsg.googlegroups.com...

> The design is to use port 30101, this is not being used as a web
> server in the normal sense. We do not want to use port 80. The network
> hardware, natting, port forwarding etc is working fine. I have done a
> trace on the packets and the destination port on them is being
> assigned correctly as port 30101. Tomcat is misbehaving as far as I
> and another senior unix admin can tell.

every web browser, internet explorer, seagull, firefox, safari, opera, or
whatever you use, uses port 80 when they have a http: starting the url. So
the choices you have are

a) coding every url from http://myserver/something to
http://myserver/something:30101

b) telling your tomcat to listen to port 80

c) use port forwarding (which works fine as you said)

d) i dont know how web browers could be setup different so that they use
port 30101 for http:. But this would make your browser incompatible with the
rest of the world.

e) maybee your port forwarder could be setup to do some "selective
forwarding", so that http://myserver/something could be handled different
than other urls.

I dont know in-depth, but maybee ms isa server could do such a selective
forwarding.
http://www.kleinurl.de/?dkd0bjld
http://www.microsoft.com/isaserver/default.mspx
http://www.microsoft.com/technet/isa/default.mspx
http://support.microsoft.com/ph/2108/ph/2108

If you find a better way, please let us know ;-) We always are curyous
(curious ?) to hear new things.

greetings from germany
Chris

Re: Having trouble getting apache to listen without the port number appended

On Sep 7, 1:44 pm, Christian Stüben wrote:
> Hi Bozo,
>
> "bozo" schrieb im Newsbeitragnews:1189159458.83823=
626560@r29g2000hsg.googlegroups.com...
>
> > The design is to use port 30101, this is not being used as a web
> > server in the normal sense. We do not want to use port 80. The network
> > hardware, natting, port forwarding etc is working fine. I have done a
> > trace on the packets and the destination port on them is being
> > assigned correctly as port 30101. Tomcat is misbehaving as far as I
> > and another senior unix admin can tell.
>
> every web browser, internet explorer, seagull, firefox, safari, opera, or
> whatever you use, uses port 80 when they have a http: starting the url. So
> the choices you have are
>
> a) coding every url fromhttp://myserver/somethingtohttp://myserver/someth=
ing:30101
>
> b) telling your tomcat to listen to port 80
>
> c) use port forwarding (which works fine as you said)
>
> d) i dont know how web browers could be setup different so that they use
> port 30101 for http:. But this would make your browser incompatible with =
the
> rest of the world.
>
> e) maybee your port forwarder could be setup to do some "selective
> forwarding", so thathttp://myserver/somethingcould be handled different
> than other urls.
>
> I dont know in-depth, but maybee ms isa server could do such a selective
> forwarding.http://www.kleinurl.de/?dkd0bjldhttp://www.micros oft.com/isase=
rver/default.mspxhttp://www.microsoft.com/technet/isa/defaul t.mspxhttp://su=
pport.microsoft.com/ph/2108/ph/2108
>
> If you find a better way, please let us know ;-) We always are curyous
> (curious ?) to hear new things.
>
> greetings from germany
> Chris
Thanks again.
I have discovered that tomcat is part of some software that we have
bought and we cannot make any tweaks to it at all.So we have to look
for another solution.