Lighttpd

https://git.lighttpd.net/lighttpd/lighttpd1.4/src/commit/230a4f53a4d136279a678c4f2cef17fea4f3f2d6/src/mod_dirlisting.c#L759-L764

3 bits (25-22) are not enough to encode 12 months. Currently 2025-Jan is encoded as ((2025<<25) | (0<<22)) i.e. ((2024*8 + 8)<<22), while 2024-Oct is ((2024*8 + 9)<<22), so sorting by mtime will believe 2024-Oct is newer than 2025-Jan.

A quick fix can be change 25 in `parseInt(d<sup>0</sup>)*(1<<25)` into 26.

diff --git a/src/mod_dirlisting.c b/src/mod_dirlisting.c
index d8baf381..f3de27f0 100644
--- a/src/mod_dirlisting.c
+++ b/src/mod_dirlisting.c
@@ -756,7 +756,7 @@ static const char js_simple_table_resort[] = \
 "    el.dataset.value = -1;\n" \
 "  } else {\n" \
 "   var d = li_date_regex.exec(get_inner_text(el));\n" \
-"   el.dataset.value = (parseInt(d[1])*(1<<25))\n" \
+"   el.dataset.value = (parseInt(d[1])*(1<<26))\n" \
 "     + ( (li_mon_num(d[2])<<22)\n" \
 "        |(parseInt(d[3])  <<17)\n" \
 "        |(parseInt(d[4])  <<12)\n" \

A more advanced fix (and better, IMO) is, why bother tweaking with bit operations instead of just utilizing JS Date class? The calculated mtime can be a reasonable value for some further functionalities if using JS Date.

diff --git a/src/mod_dirlisting.c b/src/mod_dirlisting.c
index d8baf381..55cd28a7 100644
--- a/src/mod_dirlisting.c
+++ b/src/mod_dirlisting.c
@@ -756,12 +756,10 @@ static const char js_simple_table_resort[] = \
 "    el.dataset.value = -1;\n" \
 "  } else {\n" \
 "   var d = li_date_regex.exec(get_inner_text(el));\n" \
-"   el.dataset.value = (parseInt(d[1])*(1<<25))\n" \
-"     + ( (li_mon_num(d[2])<<22)\n" \
-"        |(parseInt(d[3])  <<17)\n" \
-"        |(parseInt(d[4])  <<12)\n" \
-"        |(parseInt(d[5])  << 6)\n" \
-"        |(parseInt(d[6])) );\n" \
+"   el.dataset.value = new Date(\n" \
+"     parseInt(d[1]), li_mon_num(d[2]), parseInt(d[3]),\n" \
+"     parseInt(d[4]), parseInt(d[5]), parseInt(d[6])\n" \
+"   ).getTime() / 1000;\n" \
 "  }\n" \
 " }\n" \
 "}\n" \