#43 ValidateFieldsHaveValues is ignored in 1.13.3 configuration

My configuration includes:
ValidateFieldsHaveValues=N

Despite this, I'm getting messages sent by another system rejected because tag 30 is present but has no value:
8=FIX.4.2
9=120
35=3
34=56391
49=KAMMJA
52=20100623-19:59:13.252
56=HUBJA
45=121008
58=Tag specified without a value
371=30
372=8
373=4
10=170

Session Level Reject: Sequence#:121008, TextTag specified without a value

My broker -- a leading US bank with much unfortunate press coverage lately -- includes tags without values in some of their responses, so I cannot upgrade to 1.13.3 without this being fixed.

Oren responded to my question about this suggesting this may be a bug:
http://www.quickfixengine.org/forum/comments.php?DiscussionID=108&page=1#Comment_452

Oren's suggestion was that there might be a workaround by moving ValidateFieldsHaveValues=N to the Default section, but that is in fact what I was trying to do in the first place.

[Alex]

I got the same problem - the behavior is different than in the previous version.

[Oren Miller]

Fixed