Closed notaco closed 3 years ago
Thanks! Unfortunately the UTF-8 stuff is vital for some implementations to work at all. I'm actually going to fix this on the server side with commit f0c0ed875558476807df6f0ce7ff0ff24f52d0cd, which will do a case-insensitive match so it will accept utf-8 or UTF-8 now, which ought to handle it.
Makes sense charset was in the documents for a reason. I thought something might be up on server side since the recent change in the httpd used. I didn't think to check case sensitivity or dig through the kismet source. I see referenced commit and am glad to have pointed it out. Thanks!
For sure, thanks - I'm sure it would have caused problems with something sooner than later too once the new webserver goes into release.
kismet version built from git master pulled last night