Re: How to map http://www.myaddress.com to http://www.myaddress.com:8000 ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.
As I stated, I am behind a firewall that is controlled remotely, so port 80 is blocked (unless your come in from within our domain).
I have successfully run it for several years on port 8000 (any port > 1024 would do) but I would like to have
it so that the port number does not need to be specified by a user wishing to access my site.
i.e., I want apache to reroute all traffic coming in on the (httpd) default port 80 to port 8000.

I don't know if this is something apache can do (i.e., if it can change the default port for http://www.mysite.com from 80 to 8000)
 or if I need to accomplish it outside of apache (find some software that maps port 80 to port 8000) ?

I'm kind of surprised (doubtful) that I would be the first person to ask this -- other sites that have to use higher ports must wonder if the added
burden of remembering/typing the port no. in the url deters users from finding their site (?)

Thanks for your help,

-Mike

On Feb 28, 2010, at 11:57 AM, Nilesh Govindarajan wrote:

On Sun, Feb 28, 2010 at 10:20 PM, Thomas, Peter <pthomas@xxxxxxxx> wrote:
No, there isn't. There are--or were--providers like dyndns that would also
do port and server re-mapping in addition to dynamic DNS aliasing.

Mike Hagerty <hagertmb@xxxxxx> wrote:

Hello.
Forgive me if this has been handled in the Archives. I've tried
searching different key words but I haven't
found anything.

I have an apache server running on port 8000.
This necessitates typing http://www.myaddress.com:8000 to get to my home
page.

I would like to be able to drop the ":8000" in the url and still have it
work.

The relevant parameters in /etc/apache/httpd.config seem to be:
Port 8000 - I set this to get around my company's firewall
#Listen - This is commented out, but from the apache docs, I think this
would just tell the server to listen on port 8000 (or the default 80)
but that the
              port no. would still need to be specified in the url
request (?)
#NameVirtualHost *:80 - From the docs I can see how this can be used so
that a single apache server can handle web requests to different
ip:ports differently,
                                       but I don't see how it could be
used for my purpose.

I guess I'm asking if there is any way to configure the server so that
http:/www.myaddress.com is assumed to be on port 8000 rather than 80 ?

Thanks!

-Mike

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


If your port 80 is open then what's the great idea behind using port 8000 unless you want to run some caching proxy like SQUID.

--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux