On 2023-10-11 03:15, Amos Jeffries wrote:
On 11/10/23 08:19, Alex Rousskov wrote:
On 2023-10-10 12:17, Francesco Chemolli wrote:
what if we removed the configure option for FOLLOW_X_FORWARDED_FOR, and
made it unconditionally part of Squid?
Some Squid deployments will silently break AFAICT.
On 2023-10-11 02:25, Amos Jeffries wrote:
Hi all,
As those familiar with Squid sources will know the documentation of
Squid is currently spread across various formats. Some custom ones, and
some very outdated.
So far we have a casual agreement amongst the core dev team to use
Markdown when
On 12/10/23 01:09, ngtech1...@gmail.com wrote:
Hey,
Not sure I understood exactly what the proposal is?
To remove the ./configure --disable-follow-x-forwarded-for build option.
Leaving the feature available to everyone.
HTH
Amos
From Amos response I understand that it will be converted
Hey,
Not sure I understood exactly what the proposal is?
>From Amos response I understand that it will be converted into some ACL which
>can be configured or not.
Right?
Eliezer
From: squid-dev On Behalf Of
Francesco Chemolli
Sent: Tuesday, October 10, 2023 19:18
To: Squid Developers
Subject
On 11/10/23 08:19, Alex Rousskov wrote:
On 2023-10-10 12:17, Francesco Chemolli wrote:
what if we removed the configure option for FOLLOW_X_FORWARDED_FOR, and
made it unconditionally part of Squid?
Some Squid deployments will silently break AFAICT.
In what way specifically?
It is on b
