shunty

whats the difference between a published url that is:

www.myserver.mylink.login.asp AND http://server1.mylink.login.asp

The reason I ask is that this is stopping my security engineer adding this published url into websense product as it only accepts www addresses. He can use the IP address instead, but once you connect to the 2nd page the name resolves with a www & then fails.

My understanding is that using a www you would obviously need to register this etc whereas you can feed a http off an lready owned www ?? is this correct ?

any help appreciated

shunty

stevencotton

There's no difference between them, and you don't need to "register" anything, it looks as if Websense is a pretty shoddy piece of work.

The "www" part of the URL is purely a hostname and means nothing, could be called steve or jesus or oooooooo. All it is is a name for a computer so other computers can find out what the IP address of it is when people type it in. What makes a computer a webserver is whether it's running webserver software, not whether it has a hostname of "www".

It sounds like Websense has the www part hard coded into it, which is so poor I can't believe it, was it written by students? Does it really not respond unless the hostname is www?

Steve.

Jeff Wiltshire

Shunty

I assume that you are having problems still with Websense V5.....

Are you aware of this info...

Unlike sites in the EIM Database, Websense cannot automatically match a
custom URL with its equivalent IP address. If you want to permit both the text
URL and the IP address of a site, you must add both to the Custom URLs/Not
Filtered list.

and this

Chapter 11: Custom URLs
To make sure that users are always filtered when accessing the site, try one of
¢º Determine whether all the URLs point to the same IP address. If so, set up
a custom URL with that IP address in place of the domain name. This
¢º Set up a separate custom URL for each URL that can be used to access
Sites with Redirected URLs
In another scenario, an organization might move its site from one server to
another, and then use the HTTP redirect feature or the HTML refresh feature
to make sure that users who request the original site are redirected to the new
site. For example, if you add the original site to the Custom URLs/Not
Filtered list, users still will be blocked when the original site directs them to
the new site, because the new site has not been set up as custom URL. In this
case, be sure to set up separate custom URLs for the original and the new
URLs.
One technique for determining whether a site you plan to custom permit
redirects to a different URL is to request the site through your browser. After
the site opens, check the URL displayed in the address bar. If the URL in the
address bar is different, set up separate permitted custom URLs for both
addresses.


Also you are aware that you must add the Custom URLs( and IP addresses) into the Not Filtered list before you add them into the Yes Lists .....and that you will need to explicitly add HTTPS (or FTP etc) if it isn't HTTP...



Does that help at all ?


Jeff

[Edited by Jeff Wiltshire - 5/27/2003 12:41:21 PM]

[Edited by Jeff Wiltshire - 5/27/2003 12:42:37 PM]

shunty

stephen - we havn't even had a response back from a support call logged last week with websense direct...

Jeff - cheers mate, just going to try that out now. I will let you know the outcome

shunty

shunty

Jeff - that worked a treat.

thanks

shunty

Jeff Wiltshire

Excellent......I'll expect a call then .....


Jeff

shunty

shunty