Forwarding. Conf diff between 2.2.STABLE5 and 2.3.STABLE2

Hello,

I have a configuration problem forwarding requests to other proxy with Squid version 2.3.S2. My configuration file was working perfectly in the previous squid version (2.2.STABLE5).

My architecture is made of 3 proxy servers.
- proxy-main, before running 2.2.STABLE5, now running 2.3.STABLE2.
- proxy-foo, a proxy to access the "foo" network.
- proxy-internet, a proxy to access the Internet.

proxy-main forwards request for the domain foo to proxy-foo.
proxy-main forwards request for the Internet to proxy-internet.
proxy-main serves itself domain1 and domain2 (proxy-main is part of domain2).

With 2.3.STABLE2, I cannot contact domain1 and domain2 servers.
For domain2 servers, request are always forwarded to proxy-internet.
Is seems that something is missing now to tell squid to use proxy-main (itself) for domain1 and domain2 requests.

Here is an extract of the configuration file I was using with SQUID 2.2.STABLE5 :

 cache_peer proxy-foo parent 8081 3130 no-query
 cache_peer proxy-internet parent 3128 3130 no-query

 cache_peer_domain proxy-foo foo
 cache_peer_domain proxy-internet !domain1

 never_direct allow all

I have read in "Changes to version 2.3.DEVEL3" that :
domain name matching : The function which checks for a match between a hostname and a domain name has been rewritten, and its behavior is now slightly different. Previously, the domain ``com'' would
match the hostname ``foo.com'', but this is no longer the case. Now, if you must write ``.com'' to match ``foo.com''.

It does not solve my problem.

The error messages indicated an address resolution problem, or

 The following error was encountered:

 Unable to forward this request at this time.
 This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that:

 The cache administrator does not allow this cache to make direct connections to origin servers, and
 All configured parent caches are currently unreachable.

Thanks for your help.

--
Laurent LECHELLE, EFFIX
l_lechelle@effix.fr