Forums

Bug? Concrete errors out on redirection only in IE/Edge browser

Permalink
This is a strange one.

A client has the following site:

http://naca.pro

On the far left of the menu bar is a link for Member Login.

This is a link to a separate site:http://member.naca.pro

On Chrome, Firefox and Safari, clicking on the Member Login link correctly takes you to the other site, which brings up the login page.

But on Internet Explorer and Edge (tested on Windows 7 and Windows 10) you get a screen with the following error message:

SessionHandler::read(): open(/tmp/sess_xxxxxxxxxxxxx, )_RDWR) failed: Permission denited (13)


I've attached a screen shot.

Any ideas? Is it a bug with interaction between concrete5 and Internet Explorer/Edge?

Thanks.

1 Attachment

 
jero replied on at Permalink Reply
jero
My guess would be that your two sites are running as separate linux/unix user IDs and that somehow IE is assuming a session cookie set for one domain is valid for the other - thus when it tries to save session information it is attempting to write to a file owned by another user. It might of course be the order in which you're visiting the sites that's significant - for example, naca.pro cookies might get applied to members.naca.pro, but not the other way round.
ctadmin replied on at Permalink Reply
With a fresh browser we seem to have no problem going to the member site.

So if that's the case how does that get fixed? Is that something where C5 has to do a browser directive in the code for session handling if it's IE?
jero replied on at Permalink Reply
jero
No. My guess is it's something to do with your web server environment or configuration. It's apparent that the owner of the PHP process that wrote the session is different to that trying to overwrite or update it. Most likely clearing all the session files out of /tmp or letting them die off or expire will fix your issue.
ctadmin replied on at Permalink Reply
But it only affects IE/Edge, not any other browser. So to me that’s a browser/C5 anomaly, not necessarily a webserver issue. Plus, IMHO, IE sucks and if it’s an issue where it works on Chrome and not on IE, I’m always going to assume IE is at fault.

;)


> On Apr 14, 2016, at 2:59 PM, concrete5 Community <discussions@concretecms.com> wrote:
ctadmin replied on at Permalink Reply
But why isn't it picking up that it's an entirely different subdomain?
ctadmin replied on at Permalink Reply
Sorry, didn't mean to sound like you should understand why IE/Edge is still a stinky browser. It's obviously an issue on their end.

I think I'm just going to try to figure out how to address via htaccess or something.

This website stores cookies on your computer. These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Privacy Policy.