From: Thomas Soddemann <[EMAIL PROTECTED]>
Date: Thu, 20 Jul 2006 13:57:42 -0600
Andrew Stevens wrote:
Another possibility - you could always use the J2EE container-provided
security and add a security-constraint to your web.xml for
/buildindex. That might be simpler than
learning the authe
Andrew Stevens wrote:
Another possibility - you could always use the J2EE container-provided
security and add a security-constraint to your web.xml for
/buildindex. That might be simpler than
learning the authentication framework or acegi if don't need to
authenticate users in the rest of y
Hello,thanks to both of you for the answers. Will look into it tomorrow; now it's time for my beauty sleep. ;)Marco2006/7/20, Andrew Stevens <
[EMAIL PROTECTED]>:>From: "Bertrand Delacretaz" <
[EMAIL PROTECTED]>>Date: Thu, 20 Jul 2006 10:13:06 +0200>>On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
Date: Thu, 20 Jul 2006 10:13:06 +0200
On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
...
http://localhost:8080//index.xml
"/>...
...which means every (outside) user could be able to start the index when
calling buildIndex. I
On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
...
http://localhost:8080//index.xml
"/>...
...which means every (outside) user could be able to start the index when
calling buildIndex. I would like to avoid that. Question is: how? ..
The clean and safest way is to use Coc
Hi,right now, I am creating a Lucene index with this entry in my sitemap: http://localhost:8080//index.xml
"/> which means every (outside) user could be able to start the index when calling bu
