Facebook
Twitter
G
GarretMott
Guest
Hi -
I freely admit to knowing little about Plesk. Bit more about IIS, but I digress.
We have a site where we've enabled URLScan (from MS) as a global filter - to keep PCI folks happier.
Problem is, URLScan is blocking any URL with a colon, so https://localahost:8443 (the shortcut to run Plesk) has issues with getting any images, so - while Plesk will run - it's got about the ugliest interface I've ever see & is largely unusable.
I have tried adding //localhost:8443 to AlwaysAllowedURLs in URLScan.ini, but no joy.
Has anyone configured URLScan to allow Plesk to be happy - or does anyone know of another way to run Plesk so it comes up as it should?
Many thanks -
Garret
I freely admit to knowing little about Plesk. Bit more about IIS, but I digress.
We have a site where we've enabled URLScan (from MS) as a global filter - to keep PCI folks happier.
Problem is, URLScan is blocking any URL with a colon, so https://localahost:8443 (the shortcut to run Plesk) has issues with getting any images, so - while Plesk will run - it's got about the ugliest interface I've ever see & is largely unusable.
I have tried adding //localhost:8443 to AlwaysAllowedURLs in URLScan.ini, but no joy.
Has anyone configured URLScan to allow Plesk to be happy - or does anyone know of another way to run Plesk so it comes up as it should?
Many thanks -
Garret
