June 2, 2020

 

I thought to use rule like following to be able to impact only audio/video streams:

if(shExpMatch(host, "*.streaming.mediaservices.windows.net"))
{
	var host_ip = dnsResolve(host);
 
	/* Check if Stream services are targets */
	if (isInNet(host_ip, '72.21.81.200', '255.255.255.255') ||
	isInNet(host_ip, '152.199.19.161', '255.255.255.255') ||
	isInNet(host_ip, '117.18.232.200', '255.255.255.255') ||
	isInNet(host_ip, '192.16.48.200', '255.255.255.255') ||
	isInNet(host_ip, '93.184.215.201', '255.255.255.255') ||
	isInNet(host_ip, '68.232.34.200', '255.255.255.255') ||
	isInNet(host_ip, '192.229.232.200', '255.255.255.255'))
	{
		returndirect;
	}

    return proxyServer;                
}

 

Then I could minimize the DNS queries. And above code is just a snap, not full .PAC file šŸ™‚

 

 

 

You May Also Like…

SharePoint Copilot Governance and Beekeeping: A Buzz-Worthy Comparison

SharePoint Copilot Governance and Beekeeping: A Buzz-Worthy Comparison

šŸ SharePoint CoPilot Governance and Beekeeping: A Buzz-Worthy Comparison. In the world of digital collaboration, SharePoint is the hive—teeming with activity, rich with resources, and vital to organizational productivity. But just like a real hive, it doesn’t thrive on chaos. That’s where governance comes in. And oddly enough, the best way to understand SharePoint governance might just be… beekeeping.

Thoughtless SharePoint Site Provisioning: The Hidden Cost of Convenience

Thoughtless SharePoint Site Provisioning: The Hidden Cost of Convenience

In the age of rapid collaboration and cloud-first strategies, provisioning SharePoint sites has never been easier. But with great power comes great potential for chaos. When sites are created without proper analysis, planning, or governance, organizations often find themselves buried under a mountain of sprawl, broken workflows, and compliance nightmares.