GWT Preventing Set-Cookie HTTP Header from Actually Setting Cookie?

If you are using RequestBuilder to contact the RPC servlet that may be the problem. Especially if you are using a different host in your request, than what you have in your browser Say navigating to localhost/app But your RequestBuilder builds a request for machinename/app/servlet If you are just using RPC without RequestBuilder you shouldn't have these problems As well if you are using RequestBuilder you may have to manually provide the cookies via setting that particular header In browser client development cookies are handled on a host name basis.

If you are using RequestBuilder to contact the RPC servlet that may be the problem. Especially if you are using a different host in your request, than what you have in your browser. Say navigating to localhost/app But your RequestBuilder builds a request for http://machinename/app/servlet.

If you are just using RPC without RequestBuilder you shouldn't have these problems.As well if you are using RequestBuilder you may have to manually provide the cookies via setting that particular header In browser client development cookies are handled on a host name basis.

As best I can tell, there is no RPC going on in the GWT sense. I am using a RequestBuilder to make a call to a server that knows nothing about GWT. As far as the GWT server that is built, I believe it is running, but it will never receive any RPC calls.

I will post the client code to give a better idea. – John Jun 15 at 0:30 Yeah I think you are going to need to handle the cookie header manually in RequestBuilder. – Terrell Plotzki Jun 15 at 1:45 You could try Cookies.

SetCookie (google-web-toolkit.googlecode. Com/svn/javadoc/latest/com/google/…, java.lang. String)) as well, but since you are using RequestBuilder this may be a long shot.

– Terrell Plotzki Jun 15 at 1:47 I would be alright, if I could grab the Cookie from the Response and put store it locally. Then, hopefully, the browser would append it to all subsequent messages. The problem is, I cannot get at the Cookie.

The Response object that is returned to me doesn't contain any Cookie accessors, only a get headers accessor. But, the headers that are returned from this call are not the same that are returned to the client from the server, including the all-important Set-Cookie header. – John Jun 15 at 18:13 I have been able to get a Set-Cookie header from a ResponseCallback: @Override public void onResponseReceived(final Request request, final Response response) { String headersString = ""; for (final Header header : response.getHeaders()) { if (header!

= null) { headersString = headersString + header.getName() + ":" + header.getValue() + "/n"; } } GWT. Log(headersString, null); } – Terrell Plotzki Jun 157 at 0:08.

This is the expected behavior of browsers: w3.org/TR/XMLHttpRequest/#the-getallresp... (GWT's Response#getHeaders simply calls getAllResponseHeaders and parses the string). If you want to get cookies, you have to use the cookies object (Cookies class in GWT); which obviously filters out httponly cookies.

I understand and agree. I, as a client, shouldn't be responsible for the Set-Cookie header. The browser should catch this, set the cookie, then pass me the rest* of the headers.

And it is working as expected when I use pure HTML and when I use JavaScript with just enough HTML to call the JavaScript. When I use GWT to make a POST to my server, everything appears to work exactly the same. GWT doesn't get the Set-Cookie header which it shouldn't have received in the first place.

However, it's like the Set-Cookie wasn't in the response. But, I have verified that it was, in fact, returned. – John Jun 24 at 16:50 How do you check whether it's set or not?

And are you sure the Set-Cookie is correct (domain and path particularly)? – Thomas Broyer Jun 24 at 17:14 I check it by going into the browser and checking for cookies. Plus, I have Firebug running and it tells me when a new cookie is set.

I know it is being sent because it works as expected with an HTTP-only sample page I created as well as a JavaScript-only (except for the bare minimum HTML to call the JavaScript) page I created. Also, Firebug shows it in the response header and the browser shows it as a stored cookie. Even when I do the GWT version, Firebug will still show it, but the browser won't set it and GWT (as expected) doesn't get it.

– John Jun 27 at 16:20.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.