[squid-users] FTP-Prompt-Behaviour changed between 3.3.11 and >=3.3.13

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/11/2014 2:07 a.m., Tom Tom wrote:
> Hi
> 
> Within squid 3.3.11 and 3.3.13 (and of course squid >3.3.13)
> changed something concerning browser-behaviour while accessing
> ftp-sites:
> 
> squid 3.3.11 ============ ftp://ftp.xxx.xxx -> User is prompted for
> username/password (TCP_DENIED/401), when anonymous-access is not
> allowed
> 
> 
> squid 3.3.13 (same config as in 3.3.11) 
> ======================================= ftp://ftp.xxx.xxx -> User
> is *not* prompted for username/password (also TCP_DENIED/401), when
> anonymous-access is not allowed.
> 
> Tested with IE and FF.
> 
> Any hints for this behaviour? Is there a way, to enforce the
> ftp-prompt?

Take a look at the HTTP response headers Squid is sending back to the
browser in those 401.

And see if there is a followup request with credentials. It may just
be the browser is doing SSO with the authentication now.

Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUXP9WAAoJELJo5wb/XPRjbXQH/21x8hke4Ot872IlbFMIlVru
NtLME6wnOB3rk+u/2e1gSiE7cdBWp6iGOIi1LWARncL84qmOb6AmsZYBNx3zpLXh
4znWM8KTSUIHWDEkbV/wJVR5XYBSbGR2onyjISc1DqA4QHkXR/+GO+ZIGhkJ/Vhf
QipOJQQQJC/9ByvtnPSXJBa5QO+h8RI7dPgkTuuImQ/vQV7X4BKFhMkoI2p3QoIV
zYXYyi9dUTV7ohdN+MxkIOSYMxgRUpED4b1bcM/Jxy4gNfwjIc2QAub1P0TNvqZ4
GCCZD4tPnAgwbb0FiEI6At5Ya/6Y5kF9zhc7OT420QFqzOUgU/i4Rn2ll8HGp3Y=
=x/fE
-----END PGP SIGNATURE-----