Bug 200463 - www/squid: 3.5.3_1 does not display FTP icons
Summary: www/squid: 3.5.3_1 does not display FTP icons
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-26 14:56 UTC by Alexander
Modified: 2015-05-27 13:07 UTC (History)
1 user (show)

See Also:
koobs: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2015-05-26 14:56:37 UTC
ftp icons ate not displayed when ftp request comes through squid (10.1-RELEASE-p10)
 steps to reproduce:
 1. install and configure squid
 2. configure browser to use squid proxy
 3. open ftp.freebsd.org in browser

access.log:  
 1432279499.717      0 10.0.80.19 TCP_MISS/404 5066 GET ftp://squidname.squiddomain:3128/squid-internal-static/icons/silk/folder.png - HIER_NONE/- text/html

cache.log: 
 date time kid1| internalStart: unknown request:
 GET /squid-internal-static/icons/silk/folder.png HTTP/1.0
 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko
 Host: ftp.freebsd.org
 Connection: keep-alive

 Additional information:
 % make showconfig
 ===> The following configuration options are available for squid-3.5.3_1:
     ARP_ACL=off: ARP/MAC/EUI based authentification
     AUTH_LDAP=off: Install LDAP authentication helpers
     AUTH_NIS=off: Install NIS/YP authentication helpers
     AUTH_SASL=off: Install SASL authentication helpers
     AUTH_SMB=off: Install SMB auth. helpers (req. Samba)
     AUTH_SQL=off: Install SQL based auth (uses MySQL)
     CACHE_DIGESTS=off: Use cache digests
     DEBUG=off: Build with extended debugging support
     DELAY_POOLS=off: Delay pools (bandwidth limiting)
     DOCS=on: Build and/or install documentation
     ECAP=off: Loadable content adaptation modules
     ESI=off: ESI support
     EXAMPLES=on: Build and/or install examples
     FOLLOW_XFF=on: Support for the X-Following-For header
     FS_AUFS=off: AUFS (threaded-io) support
     FS_DISKD=off: DISKD storage engine controlled by separate service
     FS_ROCK=off: ROCK storage engine
     HTCP=off: HTCP support
     ICAP=off: the ICAP client
     ICMP=off: ICMP pinging and network measurement
     IDENT=off: Ident lookups (RFC 931)
     IPV6=off: IPv6 protocol support
     KQUEUE=on: Kqueue(2) support
     LARGEFILE=on: Support large (>2GB) cache and log files
     LAX_HTTP=off: Do not enforce strict HTTP compliance
     NETTLE=off: Nettle MD5 algorithm support
     SNMP=off: SNMP support
     SSL=off: SSL gatewaying support
     SSL_CRTD=off: Use ssl_crtd to handle SSL cert requests
     STACKTRACES=off: Enable automatic backtraces on fatal errors
     TP_IPF=off: Transparent proxying with IPFilter
     TP_IPFW=off: Transparent proxying with IPFW
     TP_PF=off: Transparent proxying with PF
     VIA_DB=off: Forward/Via database
     WCCP=off: Web Cache Coordination Protocol
     WCCPV2=off: Web Cache Coordination Protocol v2
====> Install Kerberos authentication helpers: you have to select exactly one of them
     GSSAPI_NONE=on: Build without Kerberos support
     GSSAPI_BASE=off: Build with Kerberos support from base
     GSSAPI_HEIMDAL=off: Build with Kerberos support from security/heimdal
     GSSAPI_MIT=off: Build with Kerberos support from security/krb5
===> Use 'make config' to modify these settings
Comment 1 Pavel Timofeev 2015-05-27 03:44:37 UTC
Why do you think it's related to port and not to squid itself? Did you try same squid version on linux, for example?
Comment 2 Alexander 2015-05-27 05:58:06 UTC
It seems to be bug in squid http://bugs.squid-cache.org/show_bug.cgi?id=4132
There are 2 ways to deal with it:
1. wait for release where this issue is fixed (hopefully will be included in 3.5.5)
2. implement patch http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-13835.patch (I never tested this)

Option 1 is acceptable for me.
Comment 3 Pavel Timofeev 2015-05-27 07:50:23 UTC
(In reply to Alexander from comment #2)

Good, thank you!
I think this PR can be closed.
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2015-05-27 13:07:29 UTC
Closing issue pending next (3.5.5) upstream release