Hi all
I have run across a problem, where the last few bytes of the entity body
are not transferred to the client.
The problem occurs if the number of characters in the entity body does
not match the number of bytes in the encoded string (in my case UTF-8).
Example 1:
@GET
@Produces(
BTW: I was using Restlet 1.1rc2, the reported tests.
Roman
Roman Geus wrote:
Hi all
I have run across a problem, where the last few bytes of the entity
body are not transferred to the client.
The problem occurs if the number of characters in the entity body does
not match the number of byt
Pretty sure that's a bug. Content-length is supposed to be octets (HTTP
spec 4.4.3, http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html)
On Fri, Sep 26, 2008 at 5:29 AM, Roman Geus <[EMAIL PROTECTED]> wrote:
> Is it a bug or a feature?
>
> Cheers,
> Roman
>
>
Hi Roman,
when I have a look at the source code of the StringRepresentation class,
I notice that the length is computed on via the "getBytes" method which
should calcute the correct length.
I have a few questions: as I think that this code
("Response.ok().entity(result).build();") is certainl
Hi Thierry
To my knowledge my example uses only Restlet classes, i.e.
javax.ws.rs.core.Response
I think the problem could be in
org.restlet.ext.jaxrs.internal.provider.StringProvider.getSize(...). It
returns the number of characters, but the docs of
javax.ws.rs.ext.MessageBodyWriter.getSize
Hi Roman,
yes, you are right, this was a bug in the StringProvider. It's fixed in
the trunk now. Does it work for you now?
Sorry for the delay, because I have to do a lot of other things in the
moment I do not read the mailing list emails fast. If you note in the
subject that it's a problem fo
Hi Stephan
Thanks for quick fix! It works now for me. At first I wasn't sure if
JAX-RS was responsible, so I didn't mention it in the subject line.
Cheers,
Roman
Stephan Koops wrote:
Hi Roman,
yes, you are right, this was a bug in the StringProvider. It's fixed
in the trunk now. Does it wo
7 matches
Mail list logo
