Hi Sig, Thanks for doing all that detective work. Unfortunately I don't have an Ubuntu box to test on. :-(
I wonder if there is some place that I pull in the setting for the integration test user other than in the API2 code. Definitely possible. I will try to look in to it. Question if you have the time: If you add another line in the property file and assign a second user as integration admin, does that user stop working in the web interface as well? Thanks, Ethan On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <[email protected]> wrote: > Morning creative sleuth work: > > 1. Sorry, no difference between browsers: > 2. If I log on as another user, then log out in anything but root, say > "hosturl:8080/auth_view/" then no problem. > 3. If I log out and log on as api_test in root same problem on all browsers. > 4. This only for the aws instance, not for my local instance. (aws is > ubuntu, local is OS X) > 5. Did a diff between the two (local and aws) webapp folders and found > nothing different (except the .svn stuff which I removed after first > try). > 6. Did a diff between full esme directories and found no diff except > .svn folders and that esme on aws held a file named .gitignore. > > The server works though, and now I know how to get in there so I can > live with problem and assume it'll go away with a later new and fresh > install... :) > > > 2010/1/25 Richard Hirsch <[email protected]>: >> might be a lift-specific problem with those browsers. >
