Redirecting eGuide URL Requests



By: Timothy Loveridge

October 11, 2006 12:00 am

Reads: 212

Comments:0

Rating:0

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.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: Access Manager, eGuide, Technical Solutions

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Comment