Polling wuxuu leeyahay objectkiisa codsi gaar ah python-telegram-bot 22.8. Sidaas darteed, wicitaan API caadi ah oo guuleysta ma caddeeyo in getUpdates uu helay isla dariiqa proxy.

App polling, ku habee labada dariiqo:

from telegram.ext import Application

proxy_url = 'http://proxy-user:[email protected]:8080'
application = (
    Application.builder()
    .token(bot_token)
    .proxy(proxy_url)
    .get_updates_proxy(proxy_url)
    .build()
)

proxy wuxuu habayaa hawlgallada guud ee Bot API; get_updates_proxy wuxuu habayaa polling. Sii wad isticmaalka handler-yada jira iyo meerka nolosha polling ama webhook ee ku wareegsan dhismahan app.

Aqoonsiga URL waa meel-qabteyaal. Hel qiimo dhab ah iyada oo loo marayo habka aqoonsiga deployment-ka oo boqolkiiba-code garee xarfaha kaydsan ee qaybaha URL. Isticmaal scheme-ka dhabta ah ee dhexdhexaadiyaha: HTTPXRequest wuxuu aqbalaa URL-yada proxy HTTP wuxuuna taageeraa SOCKS5 iyada oo la socota ku-tiirsanaanta SOCKS ee xirmadu u baahan tahay. Liiska proxy SOCKS5 wuxuu bixiyaa musharrixiinta barta-dhamaadka ee borotokoolkaas, ma aha aqoonsiga akoonka proxy.

Haddii app-ku bixiyo object casri ah iyada oo loo marayo request ama get_updates_request, beddelkeeda si joogto ah u habee object-yadaas. Dejinta proxy ee builder iyo object codsi oo si gooni ah loo bixiyay waa gelitaanno beddel u ah dariiqa u dhigma.

Cunto-karinta Updater ee hore ee isticmaala request_kwargs iyo urllib3_proxy_kwargs waxay bartilmaameedsadaan jiil kale.

Maqaallo la xiriira