Here’s a friendly hump de bump doop bodu.
Any ideas from anybody why we would be getting authorization issues when posting data?
Thanks!
Sam
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
November 08, 2010 11:26am
Subscribe [5]#16 / Nov 10, 2010 4:50pm
Here’s a friendly hump de bump doop bodu.
Any ideas from anybody why we would be getting authorization issues when posting data?
Thanks!
Sam
#17 / Nov 10, 2010 7:08pm
Oh, sorry about that.
The best way I can explain those errors is that the session is getting lost. I’ve never seen cookies getting lost in a POST request though.
What is your session type set to? Does it help if you temporarily set it to Session IDs only?
#18 / Nov 11, 2010 10:51am
The session type is set to cookies only. According to the server admins, “we’re unable to use session id’s because we don’t know which server the request is going to hit (so if you login on production box a, the session would be local to that server)”.
Both the control panel and user session type were set to cookies only - I’ve changed them both to cookies and session id and wil monitor.
What I’m stumped on is why these issues would be occurring during a front end post. I’m trying to confirm that it’s returning the same error, but am 99% sure it is. [UPDATE] during an attempt to generate and log the error message from the front end of the site, we have been unable to duplicate the timeout… while I’m unsure of how we resolved it, it seems to be resolved, so… for now, I suppose we can ignore that part of it, which may make things a little bit more clear [/UPDATE]
This issue is driving me a little nutty - none of it makes any sense.
Please let me know if y’all have any suggestions.
Thanks!
Sam
#19 / Nov 11, 2010 2:05pm
Sam,
Your Load Balancers / Reverse Proxies need to send the actual clients IP address to the web server, generally the HTTP_X_FORWARDED_FOR header. Since ExpressionEngine is not seeing the ip address of the person surfing the site, the sessions are being lost.
My best recommendation would be to simplify your setup, and add layers of complexity only once everything is running correctly. Given that your log snippet shows a 192.168.x.x IP address, I’d start with HTTP_X_FORWARDED_FOR. If that does not solve it, my next recommendation would be to hire a sys admin who knows ExpressionEngine to work with your engineering team to come up with the ideal hosting environment for your needs.
Regards,
-greg