Apache port

Is there a way to configure apache to listen on port 80udp instead of tcp, and will the browser automatically know not to use tcp becuase I have another app thats needs to use port 80tcp?
Thanks

our would port 8080tcp work better? would the user have to specify :8080 in the url, I hope not, but then how does the browser know which server to look at. I have two servers (windows and fc2) behind a linksys router, and I need to know how to have different domains forward to different servers.

[Jman]

Edit httpd.conf and change the Listen directive. Note that you have to open port 8080. This works best with the NAT forwarding I believe you have. And yes, the domain name would have to have :8080 at the end.

Also consider Virtual Hosts.

[kosmosik]

you can do:
1] virtual host on different port (probably worse)
2] a name based virtual host (apache documentation has it covered very well)
3] a reverse proxy from one virtual host to different port on different/local machine...

but tell us exactly what is the problem here?

well, I am already using named based virtual host, but like jman said I would have to specify :8080 in the url wihch is undesirable for obvious reasons. the problem is that I am hosting several websites in development and have another application (an ip camera) that wants to use port 80 to let the owner view a store remotely.

[blammo]

I might be missing something here, but won't the camera software let you specify a different port? If it doesn't, then it must of been purchased at Toys R Us!

[crackers]

No other application should be using port 80 - that is the "default" HTTP port and is "reserved" for web servers. If you've got something else conflicting with the server, then it's typically that other thing that's wrong. And you can't use both UPD and TCP on the same port - port 80 is port 80, no matter what protocol it "talks" with.

welll thanks for actually aswering one of my post. perhaps you could help me with my boot prob in the installations section.
I gess I considier this thread done, unless someone has a brillan idea.

[blammo]

Ach, das ist a bunch of hooey!! As Crackers said, port 80 is reserved and is the default for Apache as well as IIS. Any software package that is correctly written, that needs a web port to operate, the coder should know this, and choose a port other than 80 as the default...and most likely that will be port 8080! As for the post in the installation forum that you're looking for help on, I can't seem to get a rise out of it! Would you care to elaborate?

[rkl]

We host hundreds on sites at work on a single box and you just use the VirtualHost system to allow all of them to listen on the same IP (I'll use 192.168.0.1 as an example) and port:

Listen 80  (or Port 80 if using Apache 1.X)
NameVirtualHost 192.168.0.1
<VirtualHost 192.168.0.1>
ServerName www.site1.com
DocumentRoot /path/to/site1/docs
ErrorLog /path/to/site1/logs/error_log
TransferLog /path/to/site1/logs/access_log
</VirtualHost>

<VirtualHost 192.168.0.1>
ServerName www.site2.com
DocumentRoot /path/to/site2/docs
ErrorLog /path/to/site2/logs/error_log
TransferLog /path/to/site2/logs/access_log
</VirtualHost>

You can put the www.site1.com and www.site2.com in your /etc/hosts file with IPs pointing to 192.168.0.1 and then point your apps to the names, not the IPs. You won't need to do this if you're actually an ISP hosting sites - just register the domains for real and point the www addresses to your (public) IP. Problem solved - two sites hosted on the same IP and port, but with different web addresses, document trees and log trees.

[crackers]

I re-read the part about the two boxes and I think I get what you want. You have two actual web servers (one Apache on Linux, one camera on Windows?) and you'd like them both to respond on port 80 (so folks won't have to type in port numbers).

Firstly, the Linksys (as it is) doesn't have very fancy NAT/Masquerading capabilities to be able to separate requests by URL. What you can do is configure Apache to forward particular requests to the Windows server. (You'll have to read the Apache docs on this - I did it a long time ago and it's really hazy...) You might want to combine that with the VirtualHost options mentioned above if you actually have multiple host URLs already.