Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@manifoldcf.apache.org
Received-SPF: pass (nike.apache.org: domain of daddywri@gmail.com designates
 209.85.212.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5F7592F0-151B-4C13-B50A-044723FE2CC5@gmail.com>
References: <5F7592F0-151B-4C13-B50A-044723FE2CC5@gmail.com>
Date: Wed, 9 Jan 2013 03:40:56 -0500
Message-ID: 
 <CALUFAGD_PTNdV1Mp3T8DrJB2b-vQpeDZJvGNUx68CVUmhd+1xg@mail.gmail.com>
Subject: Re: Http status code 302
From: Karl Wright <daddywri@gmail.com>
To: user@manifoldcf.apache.org
Content-Type: text/plain; charset=ISO-8859-1

It sounds like the httpclient upgrade definitely broke something.  We
should open a ticket.

But first, can you confirm what connector this is?  Is it the web
connector?  If so, I am puzzled because the web connector has always
logged any 302 return, but then queued a second document which it
subsequently fetches.

Karl

On Wed, Jan 9, 2013 at 2:10 AM, Shinichiro Abe
<shinichiro.abe.1@gmail.com> wrote:
> Hi,
>
> I'm using trunk code and crawling web site with seeds which have http://lucene.jugem.jp/?eid=39 (koji's blog --I don't obey robots.txt).
> As I'm look at Simple History, it shows 302 result code at fetch activity and doesn't ingest document.
>
> When I used MCF 1.0.1 in the same situation, Simple History showed 200 result code and MCF could ingest documents.
>
> Why does the trunk shows 302 status? Is it relevant to upgrading httpclient?
>
> Thanks in advance,
> Shinichiro Abe