Saituna biyu na iya kashe proxy middleware na Scrapy

Duba haɗaɗɗiyar jerin downloader middleware da HTTPPROXY_ENABLED kafin ƙara wani kwafin proxy middleware na ciki na Scrapy.

HttpProxyMiddleware yana cikin tsoffin saitunan downloader na Scrapy. Ba lallai ya bayyana a cikin ƙamus ɗin DOWNLOADER_MIDDLEWARES na aikin ba don samun damar.

Akwai sarrafawa biyu daban-daban da za a duba:

  • HTTPPROXY_ENABLED yana sarrafa ko an kunna ɓangaren ciki.
  • Ƙimar None don hanyar aji a cikin DOWNLOADER_MIDDLEWARES tana cire shi daga haɗaɗɗiyar sarkar middleware.

Misali, wannan yana kashe shigarwar tsoho a bayyane:

DOWNLOADER_MIDDLEWARES = {
    'scrapy.downloadermiddlewares.httpproxy.HttpProxyMiddleware': None,
}

Cire wannan soke-soke lokacin da ya kamata ɓangaren ciki ya dawo. Kada ka kwafi tsohon teburin DOWNLOADER_MIDDLEWARES_BASE cikin aikin kawai don dawo da shigarwa ɗaya; Scrapy yana haɗa tsoffin saitunansa da soke-soken aikin.

Middleware da aka kunna har yanzu yana buƙatar hanya, daga ƙimar muhalli da aka goyi bayan ko daga bayanan proxy na buƙatar. Kasancewarsa a cikin log ɗin farawa ba shine kansa ba wai rabon buƙata.

Tsofaffin sakin Scrapy sun bambanta game da lokacin da aka loda ɓangaren ba tare da ƙimar muhallin proxy ba. Ka riƙe sigar da aka shigar tare da bincike, maimakon ɗaukar lura ta tarihi daga zamanin 1.3 a matsayin ka'idar kunnawa ta yanzu.

Labarai masu alaƙa