Closed bepetersn closed 6 years ago
I haven't experienced this myself, but I'd love to hear more details about the problem and how to reproduce/fix it. Are you sure this wasn't just an issue of an invalid LI_AT cookie? On Chrome, you will receive an error saying the browser 'redirected you too many times' when the session cookie has expired.
Oh, wow. I did try to refresh the session cookie when I got an error originally. I remember still not being able to scrape a page. I guess I basically got the scraper working without knowing the cookie ahead of time...
On Mon, Jun 18, 2018 at 8:37 AM, austinoboyle notifications@github.com wrote:
I haven't experienced this myself, but I'd love to hear more details about the problem and how to reproduce/fix it. Are you sure this wasn't just an issue of an invalid LI_AT cookie? On Chrome, you will receive an error saying the browser 'redirected you too many times' when the session cookie has expired.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/austinoboyle/scrape-linkedin-selenium/issues/13#issuecomment-398076349, or mute the thread https://github.com/notifications/unsubscribe-auth/ABUzl5w-yOvYRj3sNipKnUEh1x-tthdfks5t97sOgaJpZM4Uqp1k .
-- Brian Peterson
I really appreciate your work. After using this code with much success for about a week, I starting getting an error message something like this:
I did a lot of stuff trying to fix this error, thinking LinkedIn had black-listed my IP address... I still think that's what happened. It's not exactly clear to me what was the right mixture of steps, but I did solve this issue nonetheless. I wonder if you are interested in seeing my solution to this issue. I would have to separate out my app-specific stuff from the scraping-specific code.