Yes, I can confirm that setting strictOGC = False in default.cfg fixes the problems....
'strictOGC' error on any SOS request (2.3.1-RC1)
Reproduced: the new version of parse should always check for -1 (EOF) for both open...
EventParser.parse throws OOM when end > is missing
EventParser.parse throws OOM when end > is missing