Several changes:

 - JS: Don't modify the original regex to make sure we've got a complete match.

   Instead, we will just check if the match is exactly as long as the input
   text.

   Note that if the regex used does a non-greedy match, it will not work
   correctly. However, this is an unlikely scenario.
   e.g.: if the regex is (abc)+?, the string "abcabc" would be accepted by
   the server, but not by the client (the match would be "abc" (3 chars)
   which is shorter than "abcabc" (6 chars)).

   This however prevents problems with other kinds of regexes, that may
   be more likely.
 - fix error in parsing cookies

Author: RockinRoel

src/Wt/WEnvironment.C

@@ -570,6 +570,8 @@ void WEnvironment::parseCookies(const std::string& cookie,
   boost::split(list, cookie, boost::is_any_of(";"));
   for (unsigned int i = 0; i < list.size(); ++i) {
     std::string::size_type e = list[i].find('=');
+    if (e == std::string::npos)
+      continue;
     std::string cookieName = list[i].substr(0, e);
     std::string cookieValue =
       (e != std::string::npos && list[i].size() > e + 1) ?

src/js/WRegExpValidator.js

@@ -10,7 +10,7 @@ WT_DECLARE_WT_MEMBER
 (1, JavaScriptConstructor, "WRegExpValidator",
    function(mandatory, regexp, modifiers, blankError, invalidError) {
 
-     var r = regexp ? new RegExp("^(" + regexp + ")$", modifiers) : null;
+     var r = regexp ? new RegExp(regexp, modifiers) : null;
 
      this.validate = function(text) {
        if (text.length == 0)
@@ -20,8 +20,8 @@ WT_DECLARE_WT_MEMBER
 	   return { valid: true };
 
        if (r) {
-           var result = r.test(text);
-           if (result)
+           var result = r.exec(text);
+           if (result !== null && result[0].length === text.length)
                return { valid: true };
            else
                return { valid: false, message: invalidError };