Requests-HTML 0.10.0: saita proxy na Chromium don render()

Saita hujjojin ƙaddamar da Chromium da kuma Requests lokacin da tsohon shafi na Requests-HTML ya yi nasara kafin render() sannan ya kasa bayan haka.

A cikin Requests-HTML 0.10.0, session.get() yana amfani da Requests, yayin da response.html.render() ke fara Pyppeteer kuma yawanci yana sake kai Chromium zuwa URL ɗin shafin. Nasara ta farko ba ta tabbatar da hanyar burauza ba.

Don tsohuwar muhalli mai dacewa da ke akwai da ke amfani da proxy na HTTP ba tare da tabbaci ba:

from requests_html import HTMLSession

proxy_url = 'http://proxy.example:8080'
session = HTMLSession(browser_args=[
    '--proxy-server=' + proxy_url,
])
try:
    response = session.get(
        'https://www.example.org/',
        proxies={'https': proxy_url},
        timeout=20,
    )
    response.html.render(timeout=20)
    rendered = response.html.html
finally:
    session.close()

A misalin shafin jama'a, jerin proxy na HTTP yana ba da 'yan takara don proxy_url. browser_args shine shigarwar jama'a ta maginin zaman. Kamus ɗin proxies na Requests baya cika waɗannan hujjojin Chromium.

Hakanan ba za a iya kwafa rubutun socks5h:// na Requests zuwa Chromium kai tsaye ba. Chromium yana karɓar socks5://, yana warware sunayen makoma na SOCKS5 ta hanyar proxy, kuma baya goyan bayan tabbacin sunan mai amfani da kalmar sirri na SOCKS5.

render(reload=False) yana ba da HTML ɗin da ke akwai ga burauza maimakon zuwa URL ɗin shafin. Rubuce-rubuce da ƙananan albarkatu na iya yin buƙatu har yanzu. Yana da amfani lokacin da ake yin rendering wannan amsar da gangan, amma baya mai da haɗin Requests ya zama jigilar burauza.

Labarai masu alaƙa