HTTP Error 303 causes erlang stack trace

[John Logsdon]

Hi

I kicked off a replication to couchone.com from my local couchdb by pushing 
from the local db.

It was for a 2M doc database and all was going well up until 678K entries but 
then I had a connection issue and well it's all gone horribly wrong.

Anyway basically the replication has gone from "Replicator" and I cant restart 
it. The erlang stack trace in couchdb.log looks like this:

** Reason for termination == 
** {http_request_failed,<<"unhandled response code 303">>}


[Sun, 10 Oct 2010 17:29:52 GMT] [error] [<0.17737.2>] {error_report,<0.30.0>,
    {<0.17737.2>,crash_report,
     [[{initial_call,{couch_rep_reader,init,['Argument__1']}},
       {pid,<0.17737.2>},
       {registered_name,[]},
       {error_info,
           {exit,
               {http_request_failed,<<"unhandled response code 303">>},
               [{gen_server,terminate,6},{proc_lib,init_p_do_apply,3}]}},
       {ancestors,
           [<0.17728.2>,couch_rep_sup,couch_primary_services,couch_server_sup,
            <0.31.0>]},
       {messages,
           [{'EXIT',<0.17738.2>,
                {{http_request_failed,<<"unhandled response code 303">>},
                 {gen_server,call,
                     [<0.17735.2>,next_missing_revs,infinity]}}}]},
       {links,[]},
       {dictionary,[]},
       {trap_exit,true},
       {status,running},


Have I bumped into a bug here or....????


Regards

John