Comment 4 for bug 1541691

This is definitely an issue on the server, and the impact is a 2MB dump over the network and in the logs.

I think in talking with Alex we came up with a 2 part approach.

Part 1 - make the regex smaller using ranges. That's 280814 above.

Part 2 - provide a more reasonable error which doesn't just barf up the regex, because that regex is not going to mean anything to anyone. As seen by the fact that we build it programatically and it's not even a const.