Use correct parser for session ID lengths

Can causes issues on uncommon architectures, like s390x.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/sp_config_keywords.c b/src/sp_config_keywords.c
index 7f41e38..1a23658 100644
--- a/src/sp_config_keywords.c
+++ b/src/sp_config_keywords.c
@@ -33,8 +33,8 @@ SP_PARSE_FN(parse_session) {
       {parse_empty, SP_TOKEN_ENCRYPT, &(cfg->encrypt)},
       {parse_empty, SP_TOKEN_SIMULATION, &(cfg->simulation)},
       {parse_empty, SP_TOKEN_SIM, &(cfg->simulation)},
-      {parse_uint, SP_TOKEN_SID_MIN_LENGTH, &(cfg->sid_min_length)},
-      {parse_uint, SP_TOKEN_SID_MAX_LENGTH, &(cfg->sid_max_length)},
+      {parse_ulong, SP_TOKEN_SID_MIN_LENGTH, &(cfg->sid_min_length)},
+      {parse_ulong, SP_TOKEN_SID_MAX_LENGTH, &(cfg->sid_max_length)},
       {0, 0, 0}};
 
   SP_PROCESS_CONFIG_KEYWORDS_ERR();