Forgive me if I don't understand, but it sounds like you are expecting Apache (which is your network end point) to understand your network routing and deal with it all by itself. I don't believe that reasonable without incorporating your network into the solution. Perhaps you should consider: - Adding IPs to your Apache webserver, adjusting your network routing and/or DNS, then make a virtual host respond to each IP and set serveralias as you wish. - Feed Apache additional information in order to trigger some functionality you need (cookie the users per segment, give them different DNS aliases to your web server, use rewrite rules to leverage cookies, etc). - Setting up local network segment http proxies to your Apache web server to insulate people from your network routing. - Combining the above into some sort of solution. Those are ideas, I probably can't help further. --Mark Mark Lavi, Enterprise Web Management Team @ SGI mailto:mlavi@xxxxxxx || phone:+1-650-933-7707 -----Original Message----- From: Israel Brewster [mailto:israel@xxxxxxxxxxxxxxxxxx] Sent: Wednesday, January 10, 2007 12:51 PM To: users@xxxxxxxxxxxxxxxx Subject: Re: Unwanted rewrite followup/continuationn Unfortunately, that won't work: the IP is different depending on where the machine is being accessed from. So as long as Apache insists on changing the URL to the server name, I will always have issues- it will just change depending on what I use for the server name. ----------------------------------------------- Israel Brewster Computer Support Technician Frontier Flying Service INC. 5245 Airport Industrial Rd Fairbanks, AK 99709 ----------------------------------------------- On Jan 10, 2007, at 10:13 AM, Mark Lavi wrote: > Try changing the servername directive to the IP address in > httpd.conf, I > believe that will work. > > E.g.: > > <VirtualHost *:80> > ServerName 127.0.0.1 > # etc > </VirtualHost> > > --Mark > Mark Lavi, Enterprise Web Management Team @ SGI > mailto:mlavi@xxxxxxx || phone:+1-650-933-7707 > > -----Original Message----- > From: Israel Brewster [mailto:israel@xxxxxxxxxxxxxxxxxx] > Sent: Wednesday, January 10, 2007 9:00 AM > To: users@xxxxxxxxxxxxxxxx > Subject: Unwanted rewrite followup/continuationn > > Ok, so I have managed to work around the problem below by putting the > hostname of the Apache server in the /etc/hosts file on the machines > that need to access the server by IP, so when it changes the IP to > the hostname the client can still find the server. This, however, > feels like a kludgy workaround, and wouldn't be feasible if we had > more than a couple machines that needed to access this server via ip. > Is there any way to convince Apache to NOT change the IP inn the URL > to the hostname? Thanks for any assistance that can be provided. > > ----------------------------------------------- > Israel Brewster > Computer Support Technician > Frontier Flying Service INC. > 5245 Airport Industrial Rd > Fairbanks, AK 99709 > ----------------------------------------------- > > > On Jan 8, 2007, at 9:55 AM, Israel Brewster wrote: > >> I am running into a somewhat annoying problem with Apache 1.3.29 on >> an OpenBSD 4.0 box. When attempting to access the server via IP >> address, it loads the first page fine, but after clicking a link to >> another page it rewrites the IP address in the URL to the hostname >> of the machine. This promptly results in a "server not found" >> error, as the hostname of the machine is not in DNS. How can I get >> appache to leave the URL alone? The config of this server is mostly >> still the default, aside from some authorization directives. Due to >> the network setup, simply setting the ServerName directive to the >> IP won't work, the problem there being that the IP the machine is >> accessed at is different depending on if you are accessing it from >> inside our network or outside. Actually, inside our network our >> internal DNS is set up so you can access the server by the >> hostname, but outside you need to use the IP (we don't want to make >> this server easy to find). Thank you for any assistance you can >> provide. >> ----------------------------------------------- >> Israel Brewster >> Computer Support Technician >> Frontier Flying Service INC. >> 5245 Airport Industrial Rd >> Fairbanks, AK 99709 >> ----------------------------------------------- >> >> >> >> --------------------------------------------------------------------- >> 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 > > > --------------------------------------------------------------------- > 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 --------------------------------------------------------------------- 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
|