I have tried to steer clear from answering that "statement", but since there has been a reply then I will chime in.
The simple answer is: We do test this stuff. In fact, we test it rigorously.
What happened here is that the module supports both ASP.net 1.1 and ASP.net 2.0 and is developed by people from all walks of life and locations.
As it turns out, this particular issue was not discovered, not because we failed to test it, but because it simply PASSED with flying colors on all the environments we tested it on.
It seems, however, that some environment (yet to be determined what configuration it is an issue with) are stricter than others.
At any rate, we found the problem and we posted a way to fix it. This is as much as we can do at the moment, until the next version is released.
I hope that this makes sense. Meanwhile, we will continue to try our hardest to help you and the community by delivering software that you can depend on.
Thank you for your patience and understanding.