Session identity vanishing

[peter]

*use-user-agent-for-sessions* is T

(so a session will cease to be accessible
if the client sends a different 'User-Agent' header)

But why should the user-agent change because we're dealing with a 
JSON rather than HTML return? I'm dealing with the same session, same 
browser, etc as far as the client end is concerned (ie. two 
successive clicks in the same web page).

Many thanks.


At 6:47 PM +0100 13/10/27, Edi Weitz wrote:
>Did you try to set *use-remote-addr-for-sessions* and/or
>*use-user-agent-for-sessions* to NIL?
>
>Cheers,
>Edi.
>
>On Sun, Oct 27, 2013 at 5:44 PM, peter <p2.edoc at gmail.com> wrote:
>>  Using Hunchentoot 1.2.7 on Clozure 1.9-r15808
>>  I get cookies OK when serving HTML from any host I've tried.
>>  Serving JSON on Mac (DarwinX8664) works OK too.
>>  But I lose the cookie (session  identity) when serving JSON on EC2
>>  (linuxx8664).
>>  I expect the deficiency is in my code, but am foxed.
>>  Any suggestions?
>>