Re: Data loss between HTTP client and restlet server, errors writing to non-blocking channel

Ok, problem solved. It was not a server issue after all, sorry for the noise. (It was due to creating multipart requests with HttpClient, where the file to upload was not yet completely written to disk.) -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Data-loss-be

Re: Data loss between HTTP client and restlet server, errors writing to non-blocking channel

I just tried using nginx as a reverse proxy. It doesn't seem to make any difference, data is still being lost. -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Data-loss-between-HTTP-client-and-restlet-server-errors-writing-to-non-blocking-channel-tp5720451p5721844.h

Data loss between HTTP client and restlet server, errors writing to non-blocking channel

I get these errors frequently in my restlet server log. I'm running restlet 2.0-RC04 as a standalone process. I consume the web services with Apache HTTP client 3.1. It seems to be related with serving "relatively" large pages (it seems to get more frequent). At the HTTP client side, sometimes th

Re: Chaining an authorization filter after a router

; before the resource, rather than the resource class directly. > > Avoid to mix authentication and authorization if you can. > > Best wishes, > > Bruno. > > On 29/06/10 10:15, Carles Barrobés wrote: > > > In the end it should be simpler than that. All I need to do is

Re: Chaining an authorization filter after a router

In the end it should be simpler than that. All I need to do is be able to decode the URL (same as I used as the route to the resource), match it to the current request (same as the router does) and check the parameters. Since I did not want to add authorization checks in all my resources (although

Chaining an authorization filter after a router

I'm trying to do the following: for URLs matching a pattern "/user/{username}/resource...", where username designates the resource's owner, I want to grant access only if the authenticated user matches the owner of the resource. I created a custom authorizer that looks like: import org.restlet.R

Re: Disable DTD validation doesn't seem to work (DomRepresentation)

OK thanks, I solved it with: doc.setEntityResolver(new EntityResolver() { @Override public InputSource resolveEntity(String publicId, String systemId) throws SAXException, IOException { if (systemId.contains("www.w3.org")) { retu

Re: Disable DTD validation doesn't seem to work (DomRepresentation)

Forgot to mention, this is the DOCTYPE declaration in my XHTML: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Disable-DTD-validation-doesn-t-seem-to-work-DomRepresentation-tp5230305p5230316.html Sent from the Re

Disable DTD validation doesn't seem to work (DomRepresentation)

I'm parsing an XHTML response with DomRepresentation, and it generates an exception: Exception in thread "main" java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd at org.restlet.ext.xml.XmlRep