Skip to main content.
home | support | download

Back to List Archive

Re: [swish-e] How do I index via HTTP when authentication is

From: Adam Douglas <ADouglas(at)>
Date: Thu Feb 21 2008 - 18:58:02 GMT
> Try logging in using your web browser and inspect cookies -- 
> you'll see that the cookies pertain to the domain, and that 
> https and http are two distinct domains.

There is indeed the cookie present for the domain I'm using Ahh I've never seen two different cookies based
on if https or http is used. It would be just based on the cookie name.
The domain however would not change and does not change. The use of the
cookie works perfectly fine outside of Swishe weather its http or https.
The swishe user is now logging into the site when I try to index the
authenticated side of the web site. It appears to be working but was
just asking if indeed it was by looking at the output it returned to me,

Not sure I'm following here as to what your trying to find. Swishe is
indexing now just can't via https due to a Perl issue I believe but no
clue how to resolve it. If I change the SwishSpiderConfig to use https I
can this error message as shown below. No this module is not showing up
when I list installed Perl modules. However when I attempt to install
"cpan -i LWP::Protocol::https" or "cpan -i LWP::Protocol' I get a
response that its up to date. "LWP::Protocol::https::Socket".

---- Response ---
Status: 500 Can't locate object method "new" via package
Content-Type: text/plain
Client-Date: Thu, 21 Feb 2008 18:53:06 GMT
Client-Warning: Internal response

^^^^^^^^^^^^^^^ END HEADERS ^^^^^^^^^^^^^^^^^^^^^^^^^^


This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary,privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication. Thank you.
Users mailing list
Received on Thu Feb 21 13:58:05 2008