Re: [squid-users] squid error

Hi Kinkie,

Thank you for your response. Sorry but I cannot share the hostname because
of some security reason, but the name is long (more than 10 letters).

Anyway, I found the following in squid.conf.default.

# TAG: check_hostnames
# For security and stability reasons Squid by default checks
# hostnames for Internet standard RFC compliance. If you do not want
# Squid to perform these checks then turn this directive off.
#
#Default:
# check_hostnames on

Will the "Squid Malformed Host Name Error" be eliminated if we set
"check_hostnames off" in squid.conf?
(sorry but system scan is performed irregularly and we cannot check it by
ourselves)

Thank you.

Best Regards,
Koichi Kamijo

-----------------------------------
Koichi Kamijo ($B>e[j9_at_0l(B)
IBM Research - Tokyo

From: Kinkie <gkinkie_at_gmail.com>
To: Kohichi Kamijoh/Japan/IBM_at_IBMJP
Cc: Squid Users <squid-users_at_squid-cache.org>
Date: 2014/06/17 23:52
Subject: Re: [squid-users] squid error

On Tue, Jun 17, 2014 at 4:47 PM, Kohichi Kamijoh <KAMIJOH_at_jp.ibm.com>
wrote:
> Hi Kinkie,
>
> Thank you for your quick response.
>
> This message was created by a unique system which we own.
>
> Is version 3.4 supported by Windows 7? Also, is this "Squid Malformed
Host
> Name Error" fixed by this version?

Aha!
No, unfortunately Squid 3 is not yet working on Windows. Contributions
in terms of code or sponsored development are of course welcome
towards that goal.
I was asking the question because maybe the host name _is_ malformed
after all, in this case you may want to see the check_hostnames
configuration directive
(http://www.squid-cache.org/Doc/config/check_hostnames/).

I cannot tell if the issue is fixed, because without knowing the
hostname I can't tell if this is a problem in squid or in the system
you refer to.

   Kinkie
Received on Tue Jun 17 2014 - 16:12:43 MDT