If you are having problems posting and/or logging in - make sure you force refresh a few times to clear your cache - seems some browser (like FF) are a bit aggressive with the cache. You'll need the latest JavaScript versions for things to work correctly.

If you still have problems, email me.

Yes, that worked. Thanks.

There are ways to play with HTTP headers to help avoid this. I think focusing on etag helped, if I remember former experiments correctly.

Also, you can do the "always change the js file name each time you have a new version" trick. That's very resilient and not so hard if you automate things correctly.

There are ways to play with HTTP headers to help avoid this. I think focusing on etag helped, if I remember former experiments correctly.

All of the static files we serve up should be using both modified and etags headers. You can take a look at the source code. Although it is entirely possible I have a bug in there.

I found it better to leave off last-modified, if I remember my previous experiments correctly, but it's been a while.