Hi Julien, When the session-based web crawl detects entry into a login sequence, the session cookies are cleared at that point. Essentially your symptom means that you haven't been complete about setting up your login sequence. If you make it detect the case when the session cookie is wrong, all should work properly.
This is necessary in any case because sessions do expire and there is otherwise no way to recover from that during a crawl. Karl On Mon, Jun 3, 2019 at 10:26 AM Julien Massiera < [email protected]> wrote: > Hi all, > > I was doing some tests with the Web connector, and after several tries > with different configurations of my job to crawl a session based > website, I noticed that one configuration was not working. So I debugged > the job and noticed that the connector was using a wrong session cookie. > In fact the session cookie that the connector was using, was the one of > the previous configuration of the job. I started to find how to empty > the session cookies cache but found nothing else than either suppress > and recreate the connector and job, or to manually empty the postgres > table containing the saved cookies. > > Did I miss something to easily empty the session cookies cache ? If not, > wouldn't it make sense to add a button to allow it ? > > Regards, > Julien > >
