NOUPCASE (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />Do not translate client data to upper case.<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Do not translate client data to upper case.<section end="desc" /></span> | ||
<var>NOUPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port | <var>NOUPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter indicates that no client data is to be converted to uppercase. By setting <var>NOUPCASE</var> the userid and password must be specified by the client in the correct case (probably uppercase). Note that it is possible to have lowercase userids and passwords in ''Model 204''. For example, the userids HOMER, homer and Homer would be treated as three separate userids by ''Model 204''. The <var>NOUPCASE</var> parameter simplifies the interaction between clients where names tend to be in lowercase or case-insensitive and ''Model 204'' where they tend to be in uppercase. | This parameter indicates that no client data is to be converted to uppercase. By setting <var>NOUPCASE</var> the userid and password must be specified by the client in the correct case (probably uppercase). Note that it is possible to have lowercase userids and passwords in ''Model 204''. For example, the userids HOMER, homer and Homer would be treated as three separate userids by ''Model 204''. The <var>NOUPCASE</var> parameter simplifies the interaction between clients where names tend to be in lowercase or case-insensitive and ''Model 204'' where they tend to be in uppercase. | ||
Revision as of 22:33, 29 February 2012
<section begin="desc" />Do not translate client data to upper case.<section end="desc" />
NOUPCASE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter indicates that no client data is to be converted to uppercase. By setting NOUPCASE the userid and password must be specified by the client in the correct case (probably uppercase). Note that it is possible to have lowercase userids and passwords in Model 204. For example, the userids HOMER, homer and Homer would be treated as three separate userids by Model 204. The NOUPCASE parameter simplifies the interaction between clients where names tend to be in lowercase or case-insensitive and Model 204 where they tend to be in uppercase.
The NOUPCASE parameter is the opposite of UPCASE. The default is for all ports to have UPCASE set.
Valid for WEBSERV, OPENSERV and SDS port types.