On Jan 9, 2013, at 3:51 PM, Langhorst, Brad wrote:
grr - actually - no it's not fixed
I didn't see it on a few refreshes, but apparently it was temporary - or I
was hallucinating.
These problems are tricky to debug because they involve a lot of config
fiddling and retrying. I'd suggest
On Jan 7, 2013, at 10:43 PM, Langhorst, Brad wrote:
galaxy.web.framework WARNING 2013-01-07 22:06:30,044 User logged in as
'(null)' externally, but has a cookie as 'langho...@neb.com' invalidating
session
10.254.254.86 - - [07/Jan/2013:22:06:30 -0400] GET
/api/histories/4c8cd68e0b9ed4a7
galaxy.web.framework WARNING 2013-01-07 22:06:30,044 User logged in as '(null)'
externally, but has a cookie as 'langho...@neb.commailto:langho...@neb.com'
invalidating session
10.254.254.86 - - [07/Jan/2013:22:06:30 -0400] GET
/api/histories/4c8cd68e0b9ed4a7 HTTP/1.1 403 -
