Apr-21-2020, 08:05 PM
Hi Larz,
I know what's going on now, and (in principle, at least) how to adjust the second authentication attempt appropriately. The header from the first request tells us what type of Authentication to use, in the retry.
So really all I need is to understand the nature of that header data - it looks like a simple dictionary - and proceed according to the type of Authentication returned.
If you have any other tips or links for this, supply them if you can. But I'm on the right track now, and will probably figure this out shortly.
Thanks much,
I know what's going on now, and (in principle, at least) how to adjust the second authentication attempt appropriately. The header from the first request tells us what type of Authentication to use, in the retry.
So really all I need is to understand the nature of that header data - it looks like a simple dictionary - and proceed according to the type of Authentication returned.
If you have any other tips or links for this, supply them if you can. But I'm on the right track now, and will probably figure this out shortly.
Thanks much,
(Apr-21-2020, 07:43 PM)Larz60+ Wrote: I actually never use it.
Usually the only sites that I scrape are open enough that's it's not needed.
I have run across enough instances where others use it that it was in the back of my mind, therefore the post.
requests documentation here: https://requests.readthedocs.io/en/maste...entication
shows that it should be used as I posted.
I only capture the return (in my variable response) because I usually use status_code, but also other parts of the returned structure.