Bug fix: POST body parameters were not being parsed if the Content-Type header had a character encoding supplied. Normally this doesn't happen, because IE and Firefox don't send the content type header like this, but the spec actually requires it
Bug fix: POST body parameters were not being parsed if the Content-Type header had a character encoding supplied. Normally this doesn't happen, because IE and Firefox don't send the content type header like this, but the spec actually requires it

cdauth/winstone,cdauth/winstone,cdauth/winstone