The constructor for UrlEncodedFormEntity doesn't seem to include the encoding when setting the contentType. This is in contrast to it's parent class (StringEntity) that does set the contentType. (The content-type from StringEntity doesn't stick, though, because it's set in the constructor & UrlEncodedFormEntity immediately calls setContentType in its constructor, which overwrites what StringEntity had done).
I don't know what the correct behavior should be... If I want to generate a url-encoded list of parameters, encoded in UTF-8, should that be written into the content-type like it is with a non url-encoded entity? Sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
