Hi Jerome,
Before moving to 2.2.0 I first tried 2.1.7, but that has the same issue.
We do run into a new issue with the Redirector in 2.2.0 now though. The
problem appears related to entity encoding. Responses that are encoded
by the back-end server aren't properly delivered by the proxy to the
client. Typical errors messages on the client are unexpect
end-of-streams in converters and this one:
org.apache.http.ProtocolException: The server failed to respond with a
valid HTTP response
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:151)
We haven't been able to pinpoint the source of this problem yet. Theories:
- Redirector encoding an already encoded entity a second time
- Redirector not copying/sending the proper encoding headers to the client
Any thoughts on what we can try?
Regards,
Arjohn
On 25/04/2014 03:19, Jerome Louvel wrote:
> Thanks for the feed-back Arjohn!
>
> We have completely replaced the internal HTTP connector in 2.2 so that
> certainly helped a lot.
> I don't think 2.1.7 would solve your issue but that could be
> interesting to confirm.
>
> Best,
> Jérôme
>
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3077049
