Skip to main content
Participant
September 18, 2007
Question

Disable "Jump to URL"

  • September 18, 2007
  • 2 replies
  • 1165 views
When users right click the title bar in the HTML help viewer, they get a menu containing the option "Jump to URL"

Clicking this option display a dialog box with a url box in which an address can be typed.

The chm file is on a server, and the user can type "C:\" and access the root folder on the server.

I need to either hide the title bar or disable this function.

Any one solved this one, yet?
This topic has been closed for replies.

2 replies

Peter Grainge
Community Expert
Community Expert
September 19, 2007
Sorry, no Citrix knowledge. From what you say, it seems like the problem is hand in hand with the location of the help file so I've got no other suggestions beyond what I said already, move the file.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Community Expert
September 18, 2007
Welcome to the forum.

What is the help doing in the root of the server? Put it in a folder and then the IT guys can prevent access to anywhere else with permissions.

In any case they should not be able to access the root of the server. Their browser will see C as their hard disk.

I'm no expert in this area but I don't believe your users can do what you believe they can. Have you spoken to your IT people?

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
tcwriterAuthor
Participant
September 18, 2007
Believe it. The help is not in the root directory of the server, but it is on the server. The "Jump to URL" function allows the user to jump to the root (C:\) or any other folder.

The help is on a citrix server and is run as a seamless ICA session - the users are seeing the browser/help viewer that is on the server, not their local machine, so the C drive they see is the server's, not their own. Some users don't have browsers on their local machines.

As for permissions, other applications the users run need read/write access to the server, so we can't block some areas with permissions.

Thanks for the quick reply. Any ideas?