Idan aikin shine duba amsoshin HTTP da bin hanyoyin haɗi na yau da kullum, ba koyaushe ake buƙatar cikakken burauza ba. Ruby Mechanize yana fallasa proxy a kan wakilin da ke yin waɗannan buƙatun:

agent = Mechanize.new('office-route')
begin
  agent.set_proxy('proxy.example', 8080)
  page = agent.get('https://www.example.com/')
  puts page.code
ensure
  agent.shutdown
end

Wannan yana ɗauka cewa an loda ɗakin karatu na mechanize. Don ingantaccen binciken shafi na jama'a ba tare da tabbatar da proxy ba, jerin proxy na HTTP yana ba da ƙimar mai masauki/tashar jiragen ruwa da suka dace don misalin. Hanyar proxy kuma tana karɓar sunan mai amfani da kalmar sirri a matsayin na uku da na huɗu na zaɓi lokacin da endpoint ke buƙatar su.

Sake amfani da wakilin da aka saita don buƙatun da suka shafi zaman bincike ɗaya. Yana ɗaukar cookies da tarihi da kuma saitunan cibiyar sadarwa. Canza proxy na fita ba ya haifar da sabon asali kai tsaye ko jefar da cookie na shiga.

Don zaman proxy da yawa, ba kowane ɗayansu wakilinsa maimakon canza wakili ɗaya da aka raba yayin aiki. Ɗakin karatu kuma yana rubuta sunayen haɗi na musamman lokacin da ake buƙatar haɗin SSL daban; sunan mai gini a cikin misalin yana bayyana wannan zaɓi.

Haɗa binciken URL masu alaƙa ta proxy na iya rage sake daidaitawa mara buƙata. Riƙe sakamakon da ke da alaƙa da hanyar da URL ɗin da ya samar da shi, gami da juyawa da amsoshin kuskure.

Mechanize ba ya sake yin aikin JavaScript na burauza. Yi amfani da ainihin burauza lokacin da halin da ake gwadawa ya dogara da rubutun kai, nunawa ko tabbatarwa ta musamman na burauza. Nasarar ɗaukar HTTP ta proxy yana amsa ƙaramin tambaya cewa wannan wakilin ya iya yin wannan buƙatar.

Labarai masu alaƙa