<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webscraping on Techetio</title><link>https://techetio.com/tag/webscraping/</link><description>Recent content in Webscraping on Techetio</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 24 Dec 2023 20:41:08 +0000</lastBuildDate><atom:link href="https://techetio.com/tag/webscraping/index.xml" rel="self" type="application/rss+xml"/><item><title>A Seamless Authenticated Proxy Solution For Selenium</title><link>https://techetio.com/2023/12/24/a-seamless-authenticated-proxy-solution-for-selenium/</link><pubDate>Sun, 24 Dec 2023 20:41:08 +0000</pubDate><guid>https://techetio.com/2023/12/24/a-seamless-authenticated-proxy-solution-for-selenium/</guid><description>&lt;h2 id="forwarding-requests-to-an-authenticated-proxy-with-squid"&gt;Forwarding Requests To An Authenticated Proxy With Squid&lt;/h2&gt;&#10;&lt;p&gt;In my web scraping adventures, I&amp;rsquo;ve run into the problem of attempting to use an authenticated proxy with Selenium. Using a proxy is relatively easy to configure in most web browsers, but handling authentication with proxies in selenium is far less trivial. For instance in Chrome, the solution is to create an extension with a listener on the &lt;code&gt;onAuthRequired&lt;/code&gt; event in order to know when to submit the credentials for the proxy. These hacks vary across web browsers as well.&lt;/p&gt;</description></item></channel></rss>