Ah yes. I was thinking it comes from a callback, such as test_response, that
extracts the role/right from a cookie.
Anaother option is to have it set as a parameter in @servers; the spider
begins at the same url each time, with successively higher access priveliges.
I think this will work, as it looks like the url hash, or MD5 hash of
spidered links is retained until spider_done.
---------- Original Message -----------
From: Bill Moseley <email@example.com>
To: Multiple recipients of list <firstname.lastname@example.org>
Sent: Thu, 19 Oct 2006 20:59:00 -0700 (PDT)
Subject: [SWISH-E] Re: Swish-e and authorisation-based document access
> On Thu, Oct 19, 2006 at 04:09:33PM -0700, William M Conlon wrote:
> > To get properties into the index, one needs to inject a metatag into
> > the <head> section fed to swish-e. Easy enough to do for dynamically
> > generated html, but a little trickier with filtered content. I guess
> > we would use
> > $doc_object->user_data to pass the role/right into a filter, and in
> > Pdf2HTML.pm add something like
> Where's the role data coming from?
> I haven't tried, but how about creating a subclass of
> SWISH::Filters::Pdf2HTML with your own local module and just override
> the get_pdf_headers() method?
> Bill Moseley
> Unsubscribe from or help with the swish-e list:
> Help with Swish-e:
------- End of Original Message -------
Received on Thu Oct 19 21:27:02 2006