> -----Original Message----- > From: Dougie [mailto:dougie@xxxxxxxxxxxxxx] > Sent: Wednesday, August 16, 2006 7:11 PM > To: users@xxxxxxxxxxxxxxxx > Subject: [users@httpd] Redirecting URL > > Hi all, > > Fairly new to Apache. Trying to do something pretty simple, but > have no clue what to do. > > I have a java server (that is using Jetty, internally) on my > machine. The server name is located on port 9090. I would have just > installed Apache on this same machine at port 80. If I type > in the url, > http://localhost:80, I get the message that the Apache works (a page > saying It works! is shown). If I type in the url, > http://localhost:9090, I get the webpage for my java > server... which is > correct. > > I would like it, if I typed in http://localhost:80/, I would be > redirected to http://localhost:9090. > > How can I do this? The simple answer is to redirect it (see http://httpd.apache.org/docs/2.2/mod/mod_alias.html#redirect). Something like: Redirect / http://localhost:9090 However, I'm not so sure that's really what you want. I suspect you might want a proxy... To explain the difference, consider the following analogy: A man walks into a baker's. Man: I'd like a steak please. Baker: Then you'll have to go next door to the butcher's. Man: OK (man walks out shop and into the butcher's). That's redirecting. Alternatively; A man walks into a baker's. Man: I'd like a steak please. Baker: Certainly sir. (Baker goes out the back door, goes into the butcher's, gets a steak and comes back) Baker: There you are sir. Man. Thank you... That's proxying. The difference is that with a redirect you inform the client of the new address and then the client makes a new request. With a proxy, the front-end server makes a request to the back-end on behalf of the client and the client is none the wiser. Typically, you use a redirect when you just want to point someone to another URL that you know they should be able to access, eg when updating a site, you might redirect old URLs to new ones. You use a proxy when the back-end is inaccessible to the client (eg, it's on your intranet, like an application server) or when you want to hide the source of the data from the client. Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > Any help is greatly appreciated > Doug > > > --------------------------------------------------------------------- > 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 > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. --------------------------------------------------------------------- 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
|