All,
I have a production site that I am using CKEditor on. We just released to live on 3/1 and ever since have been getting all sorts of issues related to people having their sessions dropped in the middle of what they are doing. I did all sorts of research, even opened a ticket with Microsoft (since the app is build on their technologies) but it seems that the actual culprit is the SCAYT plugin on CKEDitor...
We are using version:'3.4.2',revision:'6041'
If you have the scayt enabled, apparently cookies get written to the client browser that look something like "scayt_#...". I am able to have scayt enabled on my machine, start Fiddler, click around, and after about a minute i get kicked out due to session dying. When you look at the trace you can see right before the last request that actually had the Session cookie, there are a bunch of those "scayt" cookies. Then after the failure, all the cookies that exist are either arbitrary or "scayt".
My question is this: is there ANY way to tell the CKEditor to use a different domain or something (not sure of the terminology) so that it has no ability to remove the cookies for my session id, or do i just have to completely remove the SCAYT?
Thanks.
I have a production site that I am using CKEditor on. We just released to live on 3/1 and ever since have been getting all sorts of issues related to people having their sessions dropped in the middle of what they are doing. I did all sorts of research, even opened a ticket with Microsoft (since the app is build on their technologies) but it seems that the actual culprit is the SCAYT plugin on CKEDitor...
We are using version:'3.4.2',revision:'6041'
If you have the scayt enabled, apparently cookies get written to the client browser that look something like "scayt_#...". I am able to have scayt enabled on my machine, start Fiddler, click around, and after about a minute i get kicked out due to session dying. When you look at the trace you can see right before the last request that actually had the Session cookie, there are a bunch of those "scayt" cookies. Then after the failure, all the cookies that exist are either arbitrary or "scayt".
My question is this: is there ANY way to tell the CKEditor to use a different domain or something (not sure of the terminology) so that it has no ability to remove the cookies for my session id, or do i just have to completely remove the SCAYT?
Thanks.