Installation guide
Table Of Contents
- Gateway Customization Guide
- Contents
- Preface
- Introduction
- Setting Up the Gateway
- Gateway Installation Planning
- HTTP Server Configuration
- Creating a New Gateway Instance
- Gateway .conf File Configuration
- Configuring Gateway Clients
- Gateway Localization
- File Controlling Gateway Functionality
- Editing Entry Types
- Search Attributes, Filters, and Results
- Customizing Graphics and Color
- Parameters Defined in the .conf File
- Gateway Directives
- Introduction
- Context-Related Directives
- Entry-Related Directives
- DS_ENTRYBEGIN
- DS_ENTRYEND
- DS_ATTRIBUTE
- DS_OBJECTCLASS
- DS_VIEW_SWITCHER
- DS_SORTENTRIES
- DS_SEARCHDESC
- DS_POSTEDVALUE
- DS_EDITBUTTON
- DS_DELETEBUTTON
- DS_SAVEBUTTON
- DS_EDITASBUTTON
- DS_NEWPASSWORD
- DS_CONFIRM_NEWPASSWORD
- DS_OLDPASSWORD
- DS_HELPBUTTON
- DS_CLOSEBUTTON
- DS_BEGIN_ENTRYFORM
- DS_END_ENTRYFORM
- DS_EMIT_BASE_HREF
- DS_DNEDITBUTTON
- DS_BEGIN_DNSEARCHFORM
- DS_ATTRVAL_SET
- IF/ ELSE/ ELIF/ ENDIF
- Miscellaneous Directives
- CGI Usage
- Index
- List of Tables
changeHTML
Appendix A Parameters Defined in the .conf File 93
Format
binddnfile binddn_filename
Example
binddnfile /export/TEST/binddnfile
changeHTML
Used by the gateway to substitute ideographic space for non-breaking space (nbsp) in Asian
character sets.
Format
changeHTML nbsp_from nbsp_to charset
Example
changeHTML <space character> <space charac ter> Shift_JIS
charset
Defines the default character set for communication with HTTP clients. The default is
UTF-8 (Unicode), which supports all the characters in the Directory Server. UTF-8 is the
preferred character set; however, many browsers don’t support the UTF-8 charset or display
it poorly.
Some users may require a different character set than the one specified in using this
parameter. For these users, the
charset parameter setting may be overridden by creating a
LANG/dsgw/charset.conf file which contains the charset name. However, to receive
the correct language, users will have to configure their browsers to send the appropriate
accept-language headers.
For compatibility with HTTP clients that can’t handle an HTTP response with a
charset
parameter in the content-type, comment out this parameter in the
.conf file. This prevents
the gateway from sending an explicit charset to gateway clients. When no
charset
parameter is defined, the gateway by default transmits ISO-8859-1 (Latin-1).
The
charset parameter is ignored by current versions of Netscape Communicator and
Internet Explorer, which request the UTF-8 charset by default. Forcing these clients to use a
non-UTF-8 charset (such as Latin-1) requires the
ignoreAcceptCharsetFrom parameter.