OK. Here's the URL at the login page:
http://testintranetportal/portal/site/insideQAD/index.jsp?epi-content=LOGIN
Then, after logging in, here are a couple of URL's of content pages:
http://testintranetportal/portal/site/insideQAD/index.jsp?front_door=true&epi_menuItemID=17b4d03e0ebb0d03c0bc8ed22890307a&epi_menuID=557c013f162725a5c2046e478790307a&epi_baseMenuID=557c013f162725a5c2046e478790307a
and
http://testintranetportal/portal/site/insideQAD/index.jsp?front_door=true&epi_menuItemID=8853e4e036d9d40ecfd048922890307a&epi_menuID=b65bac56c452abf6aeda32202890307a&epi_baseMenuID=557c013f162725a5c2046e478790307a
Thanks again,
Bruce
| Neal Richter <[EMAIL PROTECTED]>
01/24/2005 12:59 PM |
|
On Sun, 23 Jan 2005, Bruce DeYoung wrote:
> Thanks Neal for the reply. Unfortunately, I cannot provide a link to the
> site since it is an intranet site only....at this time.
Post it anyway so I can take a look at it's structure. Post the login
URL then the first URL you see after a sucessful login.
> My suspicion about this is that Vignette security is handled differently
> than, say, standard Apache security. Using the -u option with htdig and
> supplying an authenticated user for our Apache-based sites works fine. I'm
> not sure how Vignette authentication works, but I do know that when you
> attempt to access the site, if your login cookie is not set, it will
> rediret to a login page and request authentication information.
Open your cookies file in the browser and clear anything associated with
this website, then relogin into the webiste and check the cookies.
> I've asked our Vignette developer to request some assistance from Vignette
> support as well.
>
> When you say "make sure cookie support is enabled", are you referring to
> something in Vignette or in htDig?
I assume you are using HtDig 3.2B6
Look at the cookies_input_file & disable_cookies settings in HtDig.
The disable_cookies is 'true' be default.
My gut feeling is that it's setting a cookie. You can take the
contents of the cookie that the browser stores and load it in to the
HtDig indexer via the cookies_input_file.
It may also be that the software checks the 'user_agent' string supplied
by the browser/indexer and may disallow access if you aren't running a
certain version of browser.
You can fake this buy setting the user_agent in HtDig to be the string
supplied by IE. Get it from your apache server weblogs.
I've seen both of these problems and worked around them this way.
> And, I understand what you're saying about using the rewrite rules...and I
> think you're right about that one. So, once I'm able to dig the site, I
> will look at the URL references and create a url_rewrite rule to remove
> the session information.
Thanks.
--
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485
