The only cause for this I can find is invalid incoming HTTP headers. I've made a change based on your exception so that in future releases these errors are silently ignored (emitting a warning to the log) so it doesn't crash your web site.
If you can capture and forward the HTTP headers that reproduce this problem, I'd love to see it.
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre