Article

Timothy Loveridge's picture
article
Reads:

3507

Score:
0
0
 
Comments:

0

Redirecting eGuide URL Requests

(View Disclaimer)

Problem

Can I have iChain automatically send a request for eguide.company.com to eguide.company.com/eGuide?

Solution

iChain is not really designed to do this. However, I can think of three ways this could be accomplished. The first two are universal ways that will work without iChain in the mix, the third is purely an iChain solution ...

Solution 1

You could have an index.html page in the root directory with a meta refresh to the /eGuide page. For example:

<META HTTP-EQUIV="Refresh" CONTENT="0; URL=/eGuide">

Solution 2

Depending on your web server flavor, you might be able to put in a server directive to do the redirect for you. An Apache server directive (using mod_alias) to accomplish this would look something like:

Redirect / /eGuide

Solution 3

Using iChain, if you require authentication for your accelerator and have FormFill enabled, you might be able to do this with a FormFill policy. Consider the following:

<urlPolicy>
<name>RedirectToeGuide</name>
<url>eguide.company.com/</url>
<actions>
<redirect>eguide.company.com/eGuide</redirect>
</actions>
<urlPolicy>

When users log in, iChain will evaluate the FormFill policies based on the URLs encountered. It will see a request for the root of the server, then process the policy to redirect the user to the specified URL. This solution is somewhat less elegant, but is an iChain-only solution.


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.




User Comments

© 2013 Novell