I would expect that the mime type is handled differently according to:
application/x-ns-proxy-autoconfig
Questions:
I am used to /etc/apache2/httpd.conf, where is the corresponding file in nethserver to check if the mime type is set correctly. Does anybody by change know how to set up the mime type handling correctly for firefox manually?
Edit:
Is there any option / command to test which proxy a system uses effectively instead of try a web request presumably blocked?
It seems like firefox doesn’t support DHCP WPAD, it uses DNS WPAD. nslookup wpad.domain.com on the client should give back your proxy server.
In my case the clients don’t use the Nethserver proxy as DNS server so I had to add an entry (wpad.domain.com pointing to the proxy) to my DNS server.
Following this, it should work for Windows System / for IE, but it does not.
I hope I do understand correctly: In my case clients do use Nethserver as proxy and DNS server (same IP).
This does not work either: I works simply if I assign proxy manually to each client - something I do not want to do
This is what I said: Direct, “aka green internal” contact seems to be possible, mostly evident by the initial part of nslookup and the fact that the file is downloaded and displayed:
> C:\Windows\System32>nslookup wpad
Server: nethserver.myname.tld
Address: 172.17.0.12
> C:\Windows\System32>ping wpad.myname.tld
Ping wird ausgeführt für wpad.myname.tld [172.17.0.12] mit 32 Bytes Daten:
Antwort von 172.17.0.12: Bytes=32 Zeit=2ms TTL=64
Antwort von 172.17.0.12: Bytes=32 Zeit=1ms TTL=64
Ping-Statistik für 172.17.0.12:
Pakete: Gesendet = 2, Empfangen = 2, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 1ms, Maximum = 2ms, Mittelwert = 1ms
> C:\Windows\System32>tracert wpad.mydomain.tld
Routenverfolgung zu wpad.mydomain.tld [172.17.0.12] über maximal 30 Abschnit
te:
1 1 ms 1 ms 1 ms nethserver.mydomain.tld [172.17.0.12]
Ablaufverfolgung beendet.
I run the proxy in transparent / SSL mode. When filters are active, the respective website responds of course a security beach (“Connection is not safe”).
In some cases strikt HTTPS is applied, aka: firefox refuses to install a security exception. Would be nice to have this for vhost, too
In some cases, where an https page is blocked, firefox allwos to install a security exception based on “blocked.nethserver.org”. As the page should be blocked, not certificate exception is required at al - just the “blocked page” needs to be displayed.
In other cases I do not understand how it works at all: pages such as https://www.test.de are displayed with the correct certificate. How does nethserver check such pages transparently?
In o
By the way: how do I get back to the normal repro for this (any other) package?
Would I miss the "regular update package if not returned / removed the test installation?
