>> На нашей фирме есть брокерская программа, которая имеет функцию поиска товара в
>> центральной базе района через Интренет. Но она не работает, не находит
>> ни одной позиции. Разработчики той программы говорят, что наш прокси не
>> пропускает SOAP-пакеты. У меня стоит Squid и настроен он стандартно... Я
>> с SOAP не сталкивался никогда, поэтому спрашиваю.
> Укажите хотя бы версию squid, и приложите его конфиг. Так тяжело сказать,
> почему у вас не работает брокерская программа.Ага, Squid version 2.7
#Recommended minimum configuration:
#acl all src all
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/32
#acl to_localhost dst 127.0.0.0/8
#
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
#acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
#acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
#acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
#
acl SSL_ports port 443 # https
acl SSL_ports port 563 # snews
acl SSL_ports port 873 # rsync
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl Safe_ports port 631 # cups
acl Safe_ports port 873 # rsync
acl Safe_ports port 901 # SWAT
acl CONNECT method CONNECT
acl office src 10.30.0.0/255.255.0.0
acl it src 10.30.0.12/255.255.255.255 10.30.0.16/255.255.255.255 10.30.0.2/255.255.255.255 10.30.0.29-10.30.0.30/255.255.255.255 10.30.0.76/255.255.255.255 10.30.0.80/255.255.255.255 10.30.30.10/255.255.255.255 10.30.7.1-10.30.7.64/255.255.255.255
acl adm src 10.30.0.102/255.255.255.255 10.30.0.150/255.255.255.255 10.30.0.25/255.255.255.255 10.30.30.27/255.255.255.255 10.30.30.55/255.255.255.255 10.30.30.51/255.255.255.255 10.30.30.52/255.255.255.255 10.30.30.61/255.255.255.255 10.30.40.1/255.255.255.255
acl bigfiles urlpath_regex \.zip$ \.rar$ \.avi$ \.mpeg$ \.mpg$ \.wma$ \.wmf$ \.mov$ \.wmv$
acl ftp proto ftp
acl liga src 10.30.0.16/255.255.255.255
acl ftp_kaspersky proto ftp
acl Inet src 10.30.0.99/255.255.255.255 10.30.100.2/255.255.255.255 10.30.100.4/255.255.255.255 10.30.233.105/255.255.255.255
acl shoutcast rep_header X-HTTP09-First-Line ^ICY.[0-9]
acl apache rep_header Server ^Apache
acl bigfilesfew urlpath_regex \.wma$ \.exe$ \.rar$ \.zip$
acl GG src 10.30.0.125/255.255.255.255 10.30.0.135/255.255.255.255 10.30.30.10/255.255.255.255 10.30.0.70/255.255.255.255
acl Downloaders src 10.30.30.52/255.255.255.255
acl electro src 10.30.30.37/255.255.255.255 10.30.30.70/255.255.255.255
# TAG: http_access
# Allowing or Denying access based on defined access lists
#
# Access to the HTTP port:
# http_access allow|deny [!]aclname ...
#
# NOTE on default values:
#
# If there are no "access" lines present, the default is to deny
# the request.
#
# If none of the "access" lines cause a match, the default is the
# opposite of the last line in the list. If the last line was
# deny, the default is allow. Conversely, if the last line
# is allow, the default will be deny. For these reasons, it is a
# good idea to have an "deny all" or "allow all" entry at the end
# of your access lists to avoid potential confusion.
#
#Default:
# http_access deny all
#
#Recommended minimum configuration:
#
# Only allow cachemgr access from localhost
# Only allow purge requests from localhost
# Deny requests to unknown ports
# Deny CONNECT to other than SSL ports
#
# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
#http_access allow localnet
# And finally deny all other access to this proxy
# TAG: http_access2
# Allowing or Denying access based on defined access lists
#
# Identical to http_access, but runs after redirectors. If not set
# then only http_access is used.
#
#Default:
# none
# TAG: http_reply_access
# Allow replies to client requests. This is complementary to http_access.
#
# http_reply_access allow|deny [!] aclname ...
#
# NOTE: if there are no access lines present, the default is to allow
# all replies
#
# If none of the access lines cause a match the opposite of the
# last line will apply. Thus it is good practice to end the rules
# with an "allow all" or "deny all" entry.
#
#Default:
# http_reply_access allow all
# TAG: icp_access
# Allowing or Denying access to the ICP port based on defined
# access lists
#
# icp_access allow|deny [!]aclname ...
#
# See http_access for details
#
#Default:
# icp_access deny all
#
#Allow ICP queries from local networks only
icp_access allow all
# TAG: htcp_access
# Allowing or Denying access to the HTCP port based on defined
# access lists
#
# htcp_access allow|deny [!]aclname ...
#
# See http_access for details
#
# NOTE: The default if no htcp_access lines are present is to
# deny all traffic. This default may cause problems with peers
# using the htcp or htcp-oldsquid options.
#
#Default:
# htcp_access deny all
#
#Allow HTCP queries from local networks only
# htcp_access allow localnet
# htcp_access deny all
# TAG: htcp_clr_access
# Allowing or Denying access to purge content using HTCP based
# on defined access lists
#
# htcp_clr_access allow|deny [!]aclname ...
#
# See http_access for details
Вариант для распечатки
on 10-Янв-12, 18:07 
