Ignore spaces when verifying the 'content-type' header

Some Java server containers parse and re-assemble the 'content-type'
header of the response, and it's not possible, nor should it matter
whether the resulting header has spaces. This change ensures the
content type is verified ignoring spaces.
#64 - also apply to dev sockjs protocol