I've had the same issue. The only workaround I've found is a bit cumbersome but
works:
@Get("json|html")
public Representation getRepresentation(Variant variant) {
if(variant.getMediaType().equals(MediaType.APPLICATION_JSON)
}
I'm not sure whether that's a regression or the inte
Hi Rickard,
Yes, we will definitely fix this issue. Thierry will likely look at it
tomorrow. Using other connectors is just a workaround. This internal connector
has increasing importance for our users so we are working hard on improving it
at each release.
FYI, we are working in the Restlet I
Hi Bruno,
It's well working , thanx...
To complete your post, below is a client code for the example we made :
Context ctx = new Context();
Client client = new Client(ctx, Protocol.HTTPS);
ClientResource service = new ClientResource("
https://192.168.2.199/./status";);
Hello Thierry,
I've changed the router query matching mode as you suggested me and it works
perfectly!
Thank you very much for your help.
Best regards.
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Problem-with-attributes-in-Restlet-2-0-tp5341461p5465010.html
Se
I was wondering whether it was possible to configure Restlet to ignore
incomplete HTTP headers when performing a request on a remote URI.
While using Restlet to crawl some sites, I've come across a fair amount of URIs
that declared an empty Pragma header ("Pragma:"). This causes the query to
fa
5 matches
Mail list logo