NOUPCASE (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
m (show "JANUS DEFINE parameter" in title)
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:NOUPCASE}}
<span class="pageSubtitle">Do not translate client data to upper case.</span>
<span class="pageSubtitle"><section begin="desc" /><section end="desc" /></span>


NOUPCASE is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
<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 <var class="product">Model 204</var>. For example, the userids HOMER, homer and Homer would be treated as three separate userids by <var class="product">Model 204</var>. The <var>NOUPCASE</var> parameter simplifies the interaction between clients where names tend to be in lowercase or case-insensitive and <var class="product">Model 204</var> where they tend to be in uppercase.


The <var>NOUPCASE</var> parameter is the opposite of <var>[[UPCASE (JANUS DEFINE parameter)|UPCASE]]</var>. The default is for all ports to have <var>UPCASE</var> set.


This parameter indicates that no client data is to be converted to upper case. By setting NOUPCASE the userid and password must be specified by the client in the correct case (probably upper case). Note that it is possible to have lower case 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 lower case or case-insensitive and ''Model 204'' where they tend to be in upper case.  
Valid for <var>[[JANUS DEFINE#type|WEBSERV]]</var>, OPENSERV and <var>[[JANUS DEFINE#type|SDS]]</var> port types.


The NOUPCASE parameter is the opposite of UPCASE. The default is for all ports to have UPCASE set.
==See also==
<ul>
<li>[[List of Janus commands]]
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]
</ul>


Valid for &P$WBSYB port types.
==References==
See: [[List of Janus commands]] | [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].


[[Category:JANUS DEFINE parameters|NOUPCASE]]
[[Category:JANUS DEFINE parameters|NOUPCASE]]

Latest revision as of 15:46, 23 April 2015

Do not translate client data to upper case.

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.

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=NOUPCASE_(JANUS_DEFINE_parameter)&oldid=77107"