03-15-2016 08:36 AM
Probably a simple answer to this question. If a site, say Google.com has both http and https, is there anything special I need to do to allow both sites? Is all I need for this is google.com and .google.com? Or do I need a regex of http?://.*google\.com instead for https?
Is the Regex only needed when you have child domains such as apps.google.com, and maps.google.com, or something like http?://.*fanniemay\.com?
Trying to replace an old outdated proxy with Ironport and transferring the whitelist is giving me a headache. It has URL's that have *domain.com:443, domain.com:443*, *domain.com, and domain.com*, but none that would transfer to Ironport without modifying them.
Just trying to determine when and where I need a regex instead of just the plain .domain.com
Solved! Go to Solution.
03-15-2016 04:44 PM
google.com and .google.com will work for http and https
.google.com will work for any sub-domain in google such as apps.google.com since '.' in front will work as a wild card.
in newer version the regular expressions may not begin or end with '.*' and cannot end with '\'
03-15-2016 04:44 PM
google.com and .google.com will work for http and https
.google.com will work for any sub-domain in google such as apps.google.com since '.' in front will work as a wild card.
in newer version the regular expressions may not begin or end with '.*' and cannot end with '\'
12-04-2017 12:25 PM
So if I want to match anything google. What is the difference between google.com by itself or .google.com by itself. Shouldn't either one match www.google.com? Or mail.google.com
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide