anybody seen 403s after a recent upgrade?
galaxy.web.framework WARNING 2013-01-07 22:06:30,044 User logged in as '(null)' externally, but has a cookie as 'langhorst@neb.com<mailto:langhorst@neb.com>' invalidating session 10.254.254.86 - - [07/Jan/2013:22:06:30 -0400] "GET /api/histories/4c8cd68e0b9ed4a7 HTTP/1.1" 403 - "http://galaxy.neb.com/history" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20100101 Firefox/17.0" i did not observe this before today… but maybe I've screwed things up in my hg fiddling today. Did anybody else see this? manual refreshes work, but automatic ones don't Brad -- Brad Langhorst langhorst@neb.com<mailto:langhorst@neb.com>
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 'langhorst@neb.com' invalidating session 10.254.254.86 - - [07/Jan/2013:22:06:30 -0400] "GET /api/histories/4c8cd68e0b9ed4a7 HTTP/1.1" 403 - "http://galaxy.neb.com/history" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20100101 Firefox/17.0"
Hi Brad, Your proxy server appears to no longer be passing the REMOTE_USER header correctly. Did anything change there? --nate
i did not observe this before today… but maybe I've screwed things up in my hg fiddling today. Did anybody else see this?
manual refreshes work, but automatic ones don't
Brad -- Brad Langhorst langhorst@neb.com
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Hmmm I reconsulted the docs and commented these lines. All seems well again after an apache restart. I had been running like this for a year or more, and only observed problems after the most recent update # RewriteCond %{IS_SUBREQ} ^false$ # RewriteCond %{LA-U:REMOTE_USER} (.+) # RewriteRule . - [E=RU:%1] RequestHeader set REMOTE_USER %{AUTHENTICATE_sAMAccountName}e I just cargo culted those in to begin with… I don't really know what they do. Brad On Jan 9, 2013, at 1:21 PM, Nate Coraor <nate@bx.psu.edu> wrote:
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 'langhorst@neb.com' invalidating session 10.254.254.86 - - [07/Jan/2013:22:06:30 -0400] "GET /api/histories/4c8cd68e0b9ed4a7 HTTP/1.1" 403 - "http://galaxy.neb.com/history" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20100101 Firefox/17.0"
Hi Brad,
Your proxy server appears to no longer be passing the REMOTE_USER header correctly. Did anything change there?
--nate
i did not observe this before today… but maybe I've screwed things up in my hg fiddling today. Did anybody else see this?
manual refreshes work, but automatic ones don't
Brad -- Brad Langhorst langhorst@neb.com
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
-- Brad Langhorst langhorst@neb.com
participants (2)
-
Langhorst, Brad -
Nate Coraor