<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: URL redirects via apache 2.2 challenge in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999560#M66772</link>
    <description>Hi, Al. &lt;BR /&gt;&lt;BR /&gt;It seems to me that you could be in need of a reverse proxy. Since you are running Apache, you might be interested in using the mod_proxy module for it. Here is a howto:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.apacheweek.com/features/reverseproxies" target="_blank"&gt;http://www.apacheweek.com/features/reverseproxies&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Also, you might be interested in using Squid for the same purpose&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.visolve.com/squid/whitepapers/reverseproxy.php" target="_blank"&gt;http://www.visolve.com/squid/whitepapers/reverseproxy.php&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I am running the apache revproxy module and it has been a lifesaver for me. It also enables me to access the webpages from behind the firewall that the servers live behind using the domain name and not the IP address or an internal DNS server. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 28 Aug 2006 05:22:48 GMT</pubDate>
    <dc:creator>Karsten Breivik_1</dc:creator>
    <dc:date>2006-08-28T05:22:48Z</dc:date>
    <item>
      <title>URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999556#M66768</link>
      <description>l'm configuring an Apache 2.2 install on linux for "name based hosting", and have created the vhosts.&lt;BR /&gt;&lt;BR /&gt;we have 10 sites that we'd like to redirect to 1 site with a directory for each of the sites.&lt;BR /&gt;&lt;BR /&gt;So what l'd like to do is redirect(302) from a URL to another URL such as:&lt;BR /&gt;&lt;BR /&gt;Redirect &lt;A href="http://www.xx.com" target="_blank"&gt;http://www.xx.com&lt;/A&gt;  &lt;A href="http://www.aaa.com/xx" target="_blank"&gt;http://www.aaa.com/xx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Redirect &lt;A href="http://www.yy.com" target="_blank"&gt;http://www.yy.com&lt;/A&gt;  &lt;A href="http://www.aaa.com/yy" target="_blank"&gt;http://www.aaa.com/yy&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The redirect option however only work from a directory to a URL/dir.&lt;BR /&gt;&lt;BR /&gt;Any  advice on how to do this hopefully easy 302?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Alan</description>
      <pubDate>Fri, 25 Aug 2006 00:17:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999556#M66768</guid>
      <dc:creator>Al_56</dc:creator>
      <dc:date>2006-08-25T00:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999557#M66769</link>
      <description>Shalom Alan,&lt;BR /&gt;&lt;BR /&gt;I'd do it with 10 directives.&lt;BR /&gt;&lt;BR /&gt;redirect &lt;A href="http://www.xx.com" target="_blank"&gt;http://www.xx.com&lt;/A&gt; &lt;A href="http://www.aa.com/xx" target="_blank"&gt;http://www.aa.com/xx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;There are options you can place directly after the redirect. This may affect whether or not the configuration works. Have you tried them?&lt;BR /&gt;&lt;BR /&gt;# redirections will not work.  See also the UseCanonicalName directive.&lt;BR /&gt;# redirections work in a sensible way.&lt;BR /&gt;# Redirect allows you to tell clients about documents which used to exist in&lt;BR /&gt;# Redirect permanent /foo &lt;A href="http://www.example.com/bar" target="_blank"&gt;http://www.example.com/bar&lt;/A&gt;&lt;BR /&gt;# 1) plain text 2) local redirects 3) external redirects&lt;BR /&gt;# We use Alias to redirect any /error/HTTP_&lt;ERROR&gt;.html.var response to&lt;BR /&gt;# The following directive disables redirects on non-GET requests for&lt;BR /&gt;# redirects for folders with DAV methods.&lt;BR /&gt;BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully&lt;BR /&gt;BrowserMatch "^WebDrive" redirect-carefully&lt;BR /&gt;BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully&lt;BR /&gt;BrowserMatch "^gnome-vfs" redirect-carefully&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;&lt;/ERROR&gt;</description>
      <pubDate>Fri, 25 Aug 2006 06:40:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999557#M66769</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-25T06:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999558#M66770</link>
      <description>Thanks mate for the advice.&lt;BR /&gt;&lt;BR /&gt;There are 50 name hosts under the same IP, and l have the same number of redirects.&lt;BR /&gt;&lt;BR /&gt;l did try this originally thinking should work, but with no luck as yet.&lt;BR /&gt;&lt;BR /&gt;So either l've placed the redirects in the wrong place in the http.conf file, or it doesn't work with "name based hosting" perhap.&lt;BR /&gt;&lt;BR /&gt;Canonial name method won't work with this application l think.&lt;BR /&gt;&lt;BR /&gt;Maybe l'll try it without the name based hosting (since it's redirecting at the domain name level).&lt;BR /&gt;&lt;BR /&gt;If anyone knows of a way to acheive this please let me know.&lt;BR /&gt;&lt;BR /&gt;Al</description>
      <pubDate>Sat, 26 Aug 2006 10:16:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999558#M66770</guid>
      <dc:creator>Al_56</dc:creator>
      <dc:date>2006-08-26T10:16:14Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999559#M66771</link>
      <description>Alan,&lt;BR /&gt;&lt;BR /&gt;My business in the US does just what you are saying, named based hosting. I'm relatively certain this can be done with any version of apache.&lt;BR /&gt;&lt;BR /&gt;I don't use redirect except to make my webmail work. Its &lt;A href="http://www.investmenttool.com/webmail" target="_blank"&gt;www.investmenttool.com/webmail&lt;/A&gt; and I use redirect to make the name webmail.investmenttool.com work properly.&lt;BR /&gt;&lt;BR /&gt;I also do extensive redirects on the web server for my employer. I believe your issue can be worked out, though it may take more extensive testing and work than is possible through the forums.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sat, 26 Aug 2006 14:42:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999559#M66771</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-26T14:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999560#M66772</link>
      <description>Hi, Al. &lt;BR /&gt;&lt;BR /&gt;It seems to me that you could be in need of a reverse proxy. Since you are running Apache, you might be interested in using the mod_proxy module for it. Here is a howto:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.apacheweek.com/features/reverseproxies" target="_blank"&gt;http://www.apacheweek.com/features/reverseproxies&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Also, you might be interested in using Squid for the same purpose&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.visolve.com/squid/whitepapers/reverseproxy.php" target="_blank"&gt;http://www.visolve.com/squid/whitepapers/reverseproxy.php&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I am running the apache revproxy module and it has been a lifesaver for me. It also enables me to access the webpages from behind the firewall that the servers live behind using the domain name and not the IP address or an internal DNS server. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Aug 2006 05:22:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999560#M66772</guid>
      <dc:creator>Karsten Breivik_1</dc:creator>
      <dc:date>2006-08-28T05:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999561#M66773</link>
      <description>It is resolved.&lt;BR /&gt;&lt;BR /&gt;l had the redirects on their own outside of the virtual host block. Once l put them into their own blocks all worked fine.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Alan</description>
      <pubDate>Thu, 31 Aug 2006 10:20:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999561#M66773</guid>
      <dc:creator>Al_56</dc:creator>
      <dc:date>2006-08-31T10:20:07Z</dc:date>
    </item>
    <item>
      <title>Re: URL redirects via apache 2.2 challenge</title>
      <link>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999562#M66774</link>
      <description>closed</description>
      <pubDate>Thu, 31 Aug 2006 10:20:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/url-redirects-via-apache-2-2-challenge/m-p/4999562#M66774</guid>
      <dc:creator>Al_56</dc:creator>
      <dc:date>2006-08-31T10:20:42Z</dc:date>
    </item>
  </channel>
</rss>

