Provide some consistent Http header value and Extension configuration parameter quoting support. <p> While QuotedStringTokenizer exists in the utils, and works great with http header values, using it in websocket-api is undesired. <ul> <li>Using QuotedStringTokenizer would introduce a dependency to the utils that would need to be exposed via the WebAppContext classloader</li> <li>ABNF defined extension parameter parsing requirements of RFC-6455 (WebSocket) ABNF, is slightly different than the ABNF parsing defined in RFC-2616 (HTTP/1.1).</li> <li>Future HTTPbis ABNF changes for parsing will impact QuotedStringTokenizer</li> </ul> It was decided to keep this implementation separate for the above reasons.