Page 1 of 1

password protected pages

Posted: Tue Dec 01, 1998 4:18 pm
by Thunderstone




Part of the web site that I index with webinator is password
protected. I have used the -U -P option to index this area & sure
enough when I click on the page titles after running a search I am
prompted for the login & password, so these pages appear to be
secure. However by clicking on the context (magnifying glass) button,
you can see the page content (in ascii), how do I disable this? I want
the pages to be accessible to our users who are allowed access but not
to everyone else who uses the search facility.


Thanks,
Karen.



password protected pages

Posted: Tue Dec 01, 1998 5:29 pm
by Thunderstone



The show-in-context page shows the ASCII formatted text that gw saved
from its walk. If you don't want the password-protected areas to show
up in a search at all, then don't walk them in the first place: exclude
them with -x or something similar.

If you want the pages to show up in the results of a search, but not
for the text to be visible in a show-context link, then you'll have to
modify the search script to exclude them, since the text must be
present in the html table for searches to work.
Modify the show-context function (<A NAME=context>) and check for
your restricted URLs where $Body is displayed: don't show it if it's
restricted. Or simply disable context views altogether: replace the
body of the <context> function with something like "No context views
available". Similarly, modify the <result> function and check for
restricted URLs before showing their abstracts with <abstract> (or
disable them).

-Kai



password protected pages

Posted: Tue Dec 01, 1998 6:57 pm
by Thunderstone




Perhaps consider creating two databases - one that does not include
the protected pages and then make this database available to your
non-members (ie, people who don't have the passwords); and another
database that includes the protected pages and which you have your
members (those with passwords) use.

How to do all this is beyond the scope of this post :) and you
might have extenuating circumstance which make this a bad idea
anyway, but I thought I'd throw this out there...

-John