Saita ProxyServer na chromedp a kan ExecAllocator

chromedp.ProxyServer zaɓi ne na ƙaddamar da burauza. Yi amfani da shi a kan allocator da ke ƙirƙirar tsarin Chromium:

opts := append(chromedp.DefaultExecAllocatorOptions[:],
    chromedp.ProxyServer("http://proxy.example:8080"),
)
allocCtx, cancelAllocator := chromedp.NewExecAllocator(
    context.Background(), opts...,
)
defer cancelAllocator()

tabCtx, cancelTab := chromedp.NewContext(allocCtx)
defer cancelTab()
err := chromedp.Run(tabCtx,
    chromedp.Navigate("https://www.example.com/"),
)

Lambar ta kasance cikin aikin da ke akwai a cikin manhajar, tare da magance kuskure na yau da kullum don err. NewContext yana gado allocator daga allocCtx. Context da aka ƙirƙira daga wani iyaye na iya ƙirƙirar wata burauza ba tare da wannan zaɓi ba.

URL ɗin proxy yana nuna mai sauraron HTTP; ana samun 'yan takara na jama'a a cikin jerin proxy na HTTP; shafin ya kasance makomar HTTPS. ProxyServer yana zuwa ga tutar --proxy-server ta Chromium, ba ga saitin proxy na net/http a Go ba.

Chromium ba ya karɓar sunan mai amfani da kalmar sirri da aka saka a cikin URL ɗin proxy da aka sa da hannu. Ƙarshen da aka tabbatar yana buƙatar tabbatarwar burauza da aka goyi bayan ko tsarin tsaka-tsaki; ƙara user:password ga wannan tuta ba daidai yake da tabbatarwar URL a abokin ciniki na HTTP ba. Tafiyar abubuwan tabbatarwa ta CDP ta Chrome hanya ɗaya ce da aka goyi bayan don magance ƙalubalen proxy da ake nufi.

Riƙe allocator a raye har sai aikin burauza ya cika. Sokewa kuma wani ɓangare ne na tsaftacewar tsari, yayin da soke tab yana iyakance yanayin burauzar da ke da alaƙa.