Set-Cookie response header not being displayed in the the rest client

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Call a GET with a 401 response
Please let me know if there is any more info required.

What is the expected output? What do you see instead?
Expect a Set-cookie header with a JSESSIONID, am getting the Set-cookie header 
using the firefox rest client

What version of the product are you using? On what operating system?
3.1, XP

Please provide any additional information below.

Response header using firefox rest client and Fiddler for a 401:
HTTP/1.1 401 Unauthorized
Date: Wed, 28 Nov 2012 14:07:26 GMT
Server: Apache/2.2.15 (Red Hat)
Set-Cookie: JSESSIONID=4B8D91D051DBE4E79C2DDFDC2908959C.xxx; Path=/xxx
WWW-Authenticate: Digest realm="xxx", qop="auth", 
nonce="MTM1NDExMzQ0NjQ2OTpjYzI5ZjQyMjM2NDI4ZWMyODMyMWJkMGNlZjBlOGZjYg=="
Content-Length: 1137
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

Response header for a 401 in the Rest-client
Date: Wed, 28 Nov 2012 14:12:30 GMT
Server: Apache/2.2.15 (Red Hat)
WWW-Authenticate: Digest realm="xxx", qop="auth", 
nonce="MTM1NDExMzc1MDgxMDpjMjdjODhhNjllZjdlY2VjMDA1Mzk1N2EzYTgyNWZiYQ=="
Content-Length: 1050
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

Original issue reported on code.google.com by jay.mcc...@ft.com on 28 Nov 2012 at 2:18

[GoogleCodeExporter]

This seems to me like an invalid issue. Firefox might be maintaining session, 
and because it is maintaining session, you might be seeing the Set-Cookie. Our 
RESTClient is completely stateless.

You may try killing the complete browser history, cache and sessions in firefox 
and try again.

Original comment by subwiz on 30 Nov 2012 at 10:38

[GoogleCodeExporter]

Thanks for the response.

I would think the Set-cookie response header being sent from our tomcat would 
still be displayed in the REST client somewhere?

I'm aware that subsequent calls won't have the cookie set unless I set it 
manually.

Original comment by jay.mcc...@ft.com on 30 Nov 2012 at 11:03

[GoogleCodeExporter]

There is only one place where it is displayed: in Response header section. I am 
displaying ALL the headers including the cookies in the Response header section 
without any conditional check.

Original comment by subwiz on 30 Nov 2012 at 11:43

[GoogleCodeExporter]

Ok, i am still not seeing the Set-cookie in the REST client, but happy to close 
if you cannot reproduce

Set-Cookie: JSESSIONID=9A8C624E1C671287553970FF05E86951.xxxxx-xxxxx-xxx; Path=/

Cheers

Original comment by jay.mcc...@ft.com on 30 Nov 2012 at 2:20

[GoogleCodeExporter]

Seems to be invalid issue.

Original comment by subwiz on 7 Dec 2013 at 3:40

• Changed state: Invalid