Hi, I'm working on an app that is using a GWT UI but accessing an existing WADL resource using a request builder and ResponseCallback.
On the initial login call to the service the remote server returns a JSessionId cookie as a Set-Cookie header parameter. In normal circumstances (ie if I access the server by making a Get from a browser directly) this cookie is visible. In GWT the cookie has disappeared. I've replicated the problem using a Jersey servlet and returning a selection of Response headers and cookies. Without fail I am unable to see any header with the name 'Set-Cookie' and by extension any cookies. This is true whether I try to access them through response.getHeaders() or Cookies.getCookie(). All other response headers are present as expected, which leads me to the conclusion that the 'Set-Cookie' header is being deliberately stripped from the response. Does this sound correct, was there a deliberate decision taken at some point to strip this header? If so, why? If not, then what is causing this behaviour. It's a major problem, as the sessionId from that cookie is needed for all subsequent calls to the server for authentication... Thanks Steve -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
