<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Squid and s3.amazonaws.com problem]]></title><description><![CDATA[<p dir="auto">hi all,</p>
<p dir="auto">I'm having strange problem with Squid and s3.amazonaws.com on my pfsense.</p>
<p dir="auto">I have configured the firewall in the way, that there is a group of trusted URLs, where proxy should not be required and the rest should be rejected: (to force users to use proxy)</p>
<p dir="auto">IPv4 TCP    LAN net    *        TrustedURLs      Web        *      none (pass selected hosts from the TrustedURLs alias)<br />
IPv4 TCP    LAN net    *        *                      Web        *      none (reject all other calls)</p>
<p dir="auto">The TrustedURLs has some hosts like:</p>
<p dir="auto">www.abcd.com<br />
www.efgh.com<br />
etc.</p>
<p dir="auto">it works perfectly for all the hosts listed there, but when I want to add s3.amazonaws.com (one if the app is using it for the images), it just doesn't work, it is being ignored and it hits the reject rule.<br />
Even if I add a rule like allowing the s3.amazonaws.com IP, it will hit the reject rule.</p>
<p dir="auto">Did anyone of you experience similar?</p>
<p dir="auto">Regards<br />
Jacek</p>
]]></description><link>https://forum.netgate.com/topic/114842/squid-and-s3-amazonaws-com-problem</link><generator>RSS for Node</generator><lastBuildDate>Mon, 12 Oct 2026 10:07:29 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/114842.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 25 Apr 2017 13:49:12 GMT</pubDate><ttl>60</ttl></channel></rss>