Custom response header item returned by JasperReports REST interface disappears

[rbrecheisen]

Hi,

I'm trying to use org.restlet.resource.ClientResource object to communicate with the REST interface of JasperReports. To preserve session state across multiple requests, JasperReports requires you to start with a login request where the username and password are passed as query params. It will then return a response with a custom header item "Set-Cookie", e.g.,

Set-Cookie: JSESSIONID=488AAF4E493E1FE5BEA25F6D71C025F3; Path=/jasperserver; HttpOnly

This header item (with JSESSIONID) must be added to the header of each subsequent request. I have a stand-alone Java program that can successfully do a multi-step communication using JSESSIONID using the Apache HTTP client directly. In our Restlet environment (with Hibernate) this doesn't work so my colleague Roland Beuker suggested I use the server-side ClientResource object which is a more proper way of handling outgoing calls to external services. I'm getting a 200 response from the JasperReports server, however, the required header item "Set-Cookie" is not there anymore.

Is it possible that this header item gets removed or filtered out somewhere in the exchange?

Kind regards,

Ralph

[rbrecheisen]

Some more info.

If I were to debug the org.restlet.engine.connector.HttpUrlConnectionCall class and check the response headers, would I see the raw, unprocessed headers received from JasperReports server? If so, it seems that these headers also miss the Set-Cookie item... this would mean that JasperReports does not even send the item. Still, I'm getting a 200 response code from JasperReports....

I hope anybody can shed some light on this issue.... :(

Ralph

[rcbeuker]

Another difference next to the standalone apache HTTP client is the Google App Engine where the Restlet code (ClientResource) is running... App Engine uses and URL Fetch service to issue HTTP and HTTPS requests;

https://cloud.google.com/appengine/docs/standard/java/outbound-requests

Could it be that this URL Fetch service clears some HTTP header fields (like the Set-Cookie: JSESSIONID=488AAF4E493E1FE5BEA25F6D71C025F3; Path=/jasperserver; HttpOnly)?