Hi Rob, thanks for the hint. How can I set the content header in my example? Im not very familiar with the api.
Regards Stefan Rob Heittman schrieb: > It looks like you're not doing anything wrong ... time to look for > server bizarreness ... ? > > If you have the ability to sniff outgoing headers (e.g. with > wireshark) try comparing the headers in your browser generated request > versus your Restlet generated request. Sometimes a minor and > insignificant difference can expose a server side bug. > > For example, last week I wasted a day tracking down a bug with a third > party web service that would return a similarly cryptic error when the > Content-Type header was "application/xml; charset=UTF-8" as opposed to > just "application/xml" ... service worked fine in some browsers, not > in others. > > - Rob > > On Thu, Apr 30, 2009 at 2:15 PM, Jon Doe <sriff...@uni-osnabrueck.de > <mailto:sriff...@uni-osnabrueck.de>> wrote: > > Doesnt matter if I take this example or use the code in my > application on the Tomcat server. I always get the following > response: > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2053872
