How to Use gdsset to Change Host Pointer

Last reviewed: April 22, 1997
Article ID: Q152998

The information in this article applies to:
  • Microsoft Internet Information Server version 1.0

SUMMARY

When you create tag files for your Gopher server, you may have to change the host name that the tag returns to the client. This article explains the correct gdsset syntax for creating tag files with different host names.

For additional information on tag files and how to create a generic tag file, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q142559
   TITLE     : Creating Tag Files for IIS Gopher Service

MORE INFORMATION

You are connecting to your Gopher server, gopher.server.edu. If you created tag files for your server contents without the -h parameter, the tag files were created with just your host name; therefore, any attempt to access a tagged item will return host name instead of the fully qualified domain name.

In those cases, to correct this problem, the tag file must be changed to return "gopher.server.edu". The syntax for gdsset.exe is shown below.

To create a tag file pointing to a different host name

For a file: "gdsset -l -s \filename -g0 -f "friendly name" -hgopher.server.edu filename". Your host name for the tag should then show gopher.server.edu.

For a directory: "gdsset -l -s \directory -g1 -f "friendly name" -hgopher.server.edu \directory". Your host name for the tag should then show gopher.server.edu.


Additional query words:
Keywords : iisconfig kbusage
Version : 1.0
Platform : WINDOWS
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.