{
  "context": "This criteria evaluates how well the engineer uses requests-cache to preserve and work with HTTP redirect chains. The focus is on proper usage of CachedSession, accessing redirect history from cached responses, and leveraging redirect aliases for cache hits on any URL in the chain.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "CachedSession usage",
      "description": "Uses requests_cache.CachedSession (or install_cache()) to create a cached session with SQLite backend for making HTTP requests",
      "max_score": 20
    },
    {
      "name": "Redirect following",
      "description": "Makes requests that follow redirects (either using default behavior or explicitly enabling allow_redirects=True)",
      "max_score": 10
    },
    {
      "name": "History attribute access",
      "description": "Accesses response.history attribute to retrieve the list of redirect responses in the chain",
      "max_score": 25
    },
    {
      "name": "Redirect chain parsing",
      "description": "Correctly extracts URL and status_code from each response in the history list to build the complete redirect chain",
      "max_score": 20
    },
    {
      "name": "Redirect alias behavior",
      "description": "Demonstrates or documents that cached responses can be retrieved using any URL from the redirect chain (initial, intermediate, or final URL), leveraging redirect alias functionality",
      "max_score": 15
    },
    {
      "name": "Cache persistence",
      "description": "Properly initializes cache with a persistent backend (e.g., SQLite with cache_name parameter) so redirect history persists across program executions",
      "max_score": 10
    }
  ]
}