Returned page for blocked content

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Returned page for blocked content

Postby jrobill » Nov 15 03 5:51 am

Whenever a user hits a page they are not allowed to their browser just displays the generic 403 page from IE saying they are not allowed to the specific site. Is there anyway of having the proxy server return a web page similar to the way the puresight page restricted page is returned for unacceptable content?

Basically, I want the proxy server to return a 403 page of my choice and not let IE make the desicion.
jrobill
 
Posts: 4
Joined: Nov 06 03 4:42 am

Postby ChrisH » Nov 15 03 9:40 am

Hello,

If you uncheck the option "Show friendly HTTP error messages" in IE (by going to Tools, Internet options, Advanced then under the "Browsing" heading, scroll down to the option) then go to restricted page again, you should see in browser, a message from WinGate saying ;

Access Denied
File not found or access denied

This is an html file that WG sends to your browser. If you want, you can make up your own "access denied" html page and store it in a shared directory that all clients can access and then have WG display it.

To change the html page you want to be displayed, you must edit part of the Qbik entries in Windows registry. If you are going to attempt to do so, I urge you to take all necessary backup precautions so things don't accidentally get screwed up. Make a copy of Qbik registry- in GateKeeper go to Options, Advanced then click on Save Registry Settings, even backup entire registry, or if OS allows it, make a restore point.

Open the registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\Wingate\Error Strings\HTTP and change the "AccessDeniedDescription" key to (but surround it with <> so it is HTML):

META HTTP-EQUIV="Refresh" CONTENT="5; URL=your_redirected_web_page.htm"

of course, instead of your_redirected_web_page put the html page you created - include the shared path. Also you could change under the same registry path the following key "AccessDeniedTitle" to

You shouldn't be here!

(or whatever). The 5 is just the length of time in seconds before the page will be redirected, so you can change that as well if needed. Now whenever a client is trying to access restricted web page they will see first for 5 seconds the message You shouldn't be here! then be redirected to the page you created. If you want to go directly to page, change the time to 0.
This page will also be displayed if you have a time restriction in place and client is attempting to access during resticted time.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby jamesc » Nov 08 05 3:47 pm

For 6.1, that registry key was removed. It can be put back in there though. That section of the Registry can be downloaded from here: http://www.wingate.com/downloads/error-strings.zip

Another way to do it with 6.1, is to ban the sites via PureSight 2; I have attached some images of the new verison.


Image
jamesc
Qbik Staff
 
Posts: 928
Joined: Apr 04 05 2:04 pm
Location: Auckland, New Zealand

Postby ChrisH » Nov 11 05 7:39 am

jamesc wrote:For 6.1, that registry key was removed.


James, do you mean with a "clean" install of WG 6.1 as opposed to an upgrade? I ask because I upgraded from WG 6.0.4 and the registry key is still there. Also that link seems to be broken.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby adrien » Nov 11 05 8:21 am

Yep, clean install doesn't write it out by default, but it is still used (i.e. read in).

Have edited the link, should now work.

Cheers

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate

Who is online

Users browsing this forum: Bing [Bot] and 75 guests