On 1/01/25 23:34, Enfal Gok wrote:
...
*The Problem:*
* When users authenticate via Kerberos, the Squid ACLs based on AD
groups are not being matched.
* All users fall into the default |http_access deny all| rule,
even if they belong to a permitted AD group.
6.
On 1/01/25 21:27, Robin Wood wrote:
I've not got time to read your whole email, but you are asking about
regular expressions.
^http:\/\/[^\.]+\.dl\.sourceforge\.net\/(.*) http://
dl.sourceforge.net.squid.internal/$1
What this means is to match the first URL and "capture" the bit at the
end,
On 1/01/25 21:21, Robin Wood wrote:
I'm going to massively over simplify things here, but you can think of
it like this.
Files with html extensions are static web pages, you write them, put
them on the server, and they are served as they are, no changes.
Asp and the others are dynamic files,
Dear Squid Support Team,
I am currently configuring Squid to use Kerberos authentication with Active
Directory (AD) group-based access control, but I am encountering an issue where
the ACLs for AD groups are not being applied correctly. Below are the details
of my setup and the challenges I am f
I've not got time to read your whole email, but you are asking about
regular expressions.
^http:\/\/[^\.]+\.dl\.sourceforge\.net\/(.*)
http://dl.sourceforge.net.squid.internal/$1
What this means is to match the first URL and "capture" the bit at the end,
the bit in brackets. This then gets rewrit
I'm going to massively over simplify things here, but you can think of it
like this.
Files with html extensions are static web pages, you write them, put them
on the server, and they are served as they are, no changes.
Asp and the others are dynamic files, they are processed by an app on the
serv
