The issue isn't with BIG-IP--it's with HTTPS as a protocol. When a client makes an HTTPS request, the HTTP host header value is encrypted. In order to present the correct certificate you must know which Host (abc.pl or abc.com.pl) the client has made the request to. In order to see the host header value, you must decrypt the SSL. To do so, you have to present a certificate to the client. You're right that this comes up frequently--unfortunately, the solution isn't an iRule, it's using separate virtual servers or a single certificate which is valid for multiple FQDN's.
Recently, posters here suggested using an SSL certificate with Subject Alternate Names (SANs) to support multiple FQDN's in the same certificate (and same VIP). We ended up getting one for our network to support domain.com and www.domain.com. Perhaps you can do this as well? Most cert authorities and browsers support SANs now.
Try searching the forums here or on a search engine for ssl certificate and SANs for details. Here's one example where Deb listed a few links: (
Click here).
Aaron
Nimbostratus
