Hi Thierry, I found that setting the representation's character set to null solves the problem. Thanks for the suggestion.
-Stuart On Tue, May 5, 2009 at 4:53 AM, Thierry Boileau <[email protected]> wrote: > Hello Stuart, > > could you check the value of : > - the representation's media type (especially the list of parameters)? > - the representation's character set? > > best regards, > Thierry Boileau > >> Hello, list! >> >> I'm using a Restlet client to interact with some very old web servers. I >> discovered one server that refuses to recognize my POST requests as valid if >> the "Content-Type" header contains a "charset=" attribute. So a request >> with this header will work: >> >> Content-Type: application/x-www-form-urlencoded >> >> But this one will not: >> >> Content-Type: application/x-www-form-urlencoded; charset=UTF-8 >> >> >> Is there a way I can force my Restlet client to omit the charset attribute >> from the Content-Type header? >> >> If you're curious, here are the server headers: >> >> Server: Microsoft-IIS/6.0 >> X-Powered-By: ASP.NET >> MicrosoftOfficeWebServer: 5.0_Pub >> X-IW-SERVER: ISYS:web/8.0 >> >> >> Thanks, >> -Stuart >> >> ------------------------------------------------------ >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2059106 >> >> > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2066868 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2071230
