Closed (fixed)
Project:
Content Access
Version:
7.x-1.2-beta1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Dec 2011 at 23:02 UTC
Updated:
9 Sep 2014 at 03:02 UTC
Jump to comment: Most recent
Comments
Comment #1
kenwest commentedSOLUTION: When using securepages, make sure /batch is handled by the same scheme as your admin pages.
ANALYSIS: Digging further, it turned out the token used when INSERTing the Batch into the batch table was different to that when SELECTing it. The difference was the session_id, because securepages was switching from HTTPS scheme to HTTP for "/batch". Preventing this dealt with the problem.
Comment #2
Schermy37 commentedI can verify that kenwest's solution works for me as well.
Comment #3
good_man commentedTagging for documenting.
Comment #4
sterndata commentedThank you! I added "batch" and "batch/*" to the list in Secure Pages and the problem has been solved.
Comment #5
truyenle commented#4 works for me too. Thank.