My cache file system is null and any memory cache should have been flushed when I rebooted right? This is a nanobsd-installation (running from a CF card).

I did however command a "flush" just to make sure.

I agree totally with you… But the issue only happens when the squid is enable... Probably it is misconfigurating... How can I start tracing the problem?

Screenshot_20160513-053306.png
Screenshot_20160513-053306.png_thumb
Screenshot_20160513-053630.png
Screenshot_20160513-053630.png_thumb
Screenshot_20160513-053333.png
Screenshot_20160513-053333.png_thumb

Ah, well neither of them start/run until you enable them, so if you get them set how you want and then turn them on, you're fine.

Do you have the "Use SafeSearch Engine" box check under Common ACL of Squidguard

that has not worked for quite a while,

before 2.3 I used DNS Resolver and created a Host Overrides

Host      Domain        IP
www     google.com 216.239.38.120

However this stoped working in 2.3

Hi
i  have same problem?

Do you have solution?

tks!

It is not possible to rewrite the Cookie header in Squid guard. You need to have the content scanning/modification engine. Typically ICAP protocol is used for this purpose like in http://docs.diladele.com/tutorials/filtering_https_traffic_squid_pfsense/index.html

As I understand it, yes. But again I am no expert.

This is actually the next thing I am delving into myself…

@PiBa:

On pfSense 2.2 it is NOT fixed, the pullrequest is still pending.. https://github.com/pfsense/pfsense-packages/pull/1236

On pfSense 2.3 it is fixed: https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-haproxy-devel/files/usr/local/pkg/haproxy/haproxy.inc#L62

Perfect, I'm on 2.3 :)

Thanks a bunch.

Thanks Guys for the help working fine now after update no errors. :) :)

Merged, thanks!

Hello Jimp,
Sorry for the late reply. Actually I upgraded and its not a NanoBSD. I didn't set the RAM disk option. Any how I upgraded another 64 bit server and had the same issue. I add proxy authentication and it started to work. Now users have to enter proxy authentication in heire web browsers.  Is there a solution.

Did you solve this? I'm having a similar issue trying to set up my reverse proxy. I have a www running on port 80 but when trying to configure a subdomain to go to another webserver on 443 I just get 404's..  ???

In the end I installed the version 2.6 of pfsense and all work fine, http and https proxy in transparent mode

Hi,

i changed my logparser.pl to extract only the root domain.
See the result in the attached image.

$user=lc $Luser; $user = Ip2Name($Lhost,$user,$Ltimestamp); next if (defined $hSkipUser{$user}); #simplified some common banner system & counters $url=$Lurl; if ($url =~ /([^:]*:\/\/)?([^\/]*\.)*([^\/\.]+\.[^\/]+)/g) {   ($site)= split /:/,$3; } else {   $site=$Lurl; } $site=$Lurl if ($site eq ""); $totalsize   {$user} +=$Lsize; $totalhit   {$user} ++;

br
Lars

log.jpg
log.jpg_thumb

well right there i cant really help you out :(