I have a owa website ssl external mapped to http internal server. Without the url filter, I can use https:// www. mywebsite.com or https:// mywebsite.com and get the right page
2010:06:07-20:50:04 gatekeeper reverseproxy: srcip="166.205.11.188" localip="10.0.0.1" size="4670" user="-" host="166.205.11.188" method="GET" statuscode="200" time="13577" url="/" server="www. mywebsite.com" referer="www. mywebsite.com/" cookie="-" set-cookie="-"
However if I enable url filter without any entry urls, I can access mywebsite.com but not www. mywebsite.com . Only thing I noticed was the stripped referrer and the no signature found[:S]
2010:06:07-20:45:07 gatekeeper reverseproxy: [Mon Jun 07 20:45:07 2010] [error] [client 166.205.11.188] No signature found, URI: www. mywebsite.com/
2010:06:07-20:45:07 gatekeeper reverseproxy: srcip="166.205.11.188" localip="10.0.0.1" size="179" user="-" host="166.205.11.188" method="GET" statuscode="403" time="3145" url="/" server="www. mywebsite.com" referer="-" cookie="-" set-cookie="-"
I thought url hardening would block everything other than the url that is in the entry url list so for example / in the entry urls would allow all access, /exchange would only allow access to mywebsite.com/exchange and the links on that page etc. But without any urls in entry URL list, I can navigate to everything (anything that doesn't have www in the url) and manipulate urls to generate 404s etc.
Also getting this in my logs which shouldn't be there
2010:06:07-20:43:23 gatekeeper reverseproxy: [Mon Jun 07 20:43:23 2010] [error] [client 166.205.11.188] Charset ISO-8859-1 not supported. Consider aliasing it?
2010:06:07-20:43:23 gatekeeper reverseproxy: [Mon Jun 07 20:43:23 2010] [warn] [client 166.205.11.188] No usable charset information; using configuration default
