I'm starting a new thread to continue this.
Our problems started about a month ago when we noticed that some sites were
extreme slow. We've found that if a proxy access rule is configured with DNS
hostnames and
one hostname has the a format like *.mycustomerwebsite.* that access to
pages like www.sommer-automatic.com, www.web2cad.de and the one listed below
are extremely slow. We want to control access to some sites on port and
domain basis. For example; everybody should be able to access a customers
ftp site and only sales should access the https B2B site. So we would
configure 2 rules like:

FTP
Type: Proxy
Proxy: HTTP
Ports: 20-21
Source: Any
Destination: *.mycustomerwebsite.* --We do *...* because many customers are
international and they have multiple hostnames for different tasks.

B2B
Type: Proxy
Proxy: HTTP
Ports: 443
Source: SalesGroup
Destination: *.mycustomerwebsite.*

We don't use URL rules because we cannot control the ports.

Can anyone verify this? Is this a bug/feature or what?

After not receiving an answer as fast as we needed one we went on to plan 2.
Plan 2 was to take all of the https sites and put them into a URL rule. The
rule looks like:

B2B
Type: URL
Source: SalesGroup
Destination:
https://*.mycustomerwebsite.*/*

https://*.mycustomerwebsite1.*/*

https://*.mycustomerwebsite2.*/*

https://*.mycustomerwebsite3.*/*

https://*.mycustomerwebsite4.*/*

https://*.mycustomerwebsite5.*/*
and so on....

Now we've noticed that the rule processes all rules that begin with http and
ftp but not with https.

Does anybody have a clue what is happening here?

Thanks,
Daryn