Server's configuration parameters on CodePage Case issues

[hmjvaline]

[size=2][color=#404040][font=Verdana, Arial, Helvetica, sans-serif][font=Lato, proxima-nova, Helvetica Neue, Arial, sans-serif][b]A while ago, in order to get the name of the interface from snmp,
 because the name encoding uses UTF-8, I set UTF-8 in the setting option of SNMP.Codepage,
and found that it had no effect.SNMP[/b].[b]Codepage[/b][/font][/font][/color][/size]


[font=Verdana, Arial, Helvetica, sans-serif]Later, it wasn't until I thought of changing UTF-8 to utf-8 that it started to work normally. [/font]
[font=Verdana, Arial, Helvetica, sans-serif]Should this input be changed to mainly uppercase, [/font]
[font=Verdana, Arial, Helvetica, sans-serif]or should it be made directly case-insensitive?[/font]

[uldis]

Hi, could you please share your test scenario, also OS and debug logs if possible, etc? We have tried from your side and were not able to replicate this issue just yet.

[hmjvaline]

I tested again and found that the problem may not be a capitalization issue. 
After we set snmp.codepage to utf-8, after I restarted the service and restarted the windows server,
 I found that it began to be unable to parse text normally again 
until I pressed the edit codepage again in the server configuratione, 
but did not modify it directly After saving, it returned to normal, 
so I think the settings of snmp.codepage may not be properly accessed when the service is restarted, 
but only take effect when the settings are saved.

[alk]

@hmjvaline said in Server's configuration parameters on CodePage Case issues:

so I think the settings of snmp.codepage may not be properly accessed when the service is restarted,

You are right, there is a bug. Will be fixed in next patch release.