Thread

I had a client that could not log in to EE admin site.

The solutions was the following from the IT department at the client’s office:

The problem was that the dynamically created page did not have a tag specifying not to cache it, so the proxy server at the ofice was caching it and breaking its functionality.  I have excluded the site from caching at the office, but you may experience problems at other sites with proxy servers, and even some ISPs that do transparent caching.  I would suggest that you may wish to have the web developer add the tags that prevent caching to prevent similar issues at other sites.

I thought this may be helpful to others.  I’ve tried to accomplish this with some meta tags in my headers of my templates but as for the admin section I may have to hack in and put following:

<meta http-equiv=“Expires” content=“0”>
<meta http-equiv=“Pragma” content=“no-cache”>
<meta http-equiv=“cache-control” content=“no-cache”>

Any idea if this will solve the problem?

Most of the EE forms will have a no cache header automatically.  I just checked my site admin cp login page- viewed the default header info in FF and I get:

content type: text/html; charset=utf-8
expires: -1
expires: Mon, 01 Jan 1970 23:59:59 GMT
pragma: no-cache

You only need it for forms and such- correct?  Or are you wanting to prevent caching of all templates?  (Which would slow things down for folks.)

I’d say check the login page she was having trouble with- see if the header info matches up to the above.  Was it a cp login page, the login page accessed via member/login- or was it a login form generated by using the login tag?

We had used the {exp:member:login_form} tag but neglected to change the meta to prevent caching. 

Hopefully our mistake helps someone else down the road!

Aha- you’re right.  That tag doesn’t end up generating a no cache header.  Hm- I wonder if it should?  I tend to think not, as it tends to be be used as an embed in a lot of pages- and in general, you want your pages to be cached.

For greatest flexibility- might be good to put in a feature request for it, I’m thinking.  On the other hand- simply changing the meta works as well, so I’d say it’s not mission critical.  Good ‘heads up’ to have in case other folks run into the issue, though!