You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #812, we discussed with @janbuchar that currently the trigger for SessionError based on status codes is not working correctly. To be more precise, when using the http client, it doesn't trigger at all.
There are several points that need to be clarified in this case:
Should blocked_status_codes in Session always take priority over any error status codes in BaseHttpClient and trigger session rotation instead of request retry?
Should additional_http_error_status_codes and ignore_http_error_status_codes be considered in the is_blocked_status_code method in Session, or should we only consider status codes defined in blocked_status_codes in Session?
Additionally: In PlaywrightCrawler, we have the opposite situation. Since we don't use an http client, we only have errors related to SessionError.
The text was updated successfully, but these errors were encountered:
After #812, we discussed with @janbuchar that currently the trigger for
SessionError
based on status codes is not working correctly. To be more precise, when using thehttp client
, it doesn't trigger at all.There are several points that need to be clarified in this case:
blocked_status_codes
inSession
always take priority over any error status codes inBaseHttpClient
and trigger session rotation instead of request retry?additional_http_error_status_codes
andignore_http_error_status_codes
be considered in theis_blocked_status_code
method inSession
, or should we only consider status codes defined inblocked_status_codes
inSession
?Additionally: In
PlaywrightCrawler
, we have the opposite situation. Since we don't use anhttp client
, we only have errors related toSessionError
.The text was updated successfully, but these errors were encountered: