On Dec 19, 2011, at 12:24 PM, Jim Johnson wrote:
Hi,
I'm seeing the same behavior. Galaxy is returning a web page rather than
the requested .bai index file for the BAM file.
In class WebApplication ( lib/galaxy/web/framework/base.py ) in __call__(
self, environ, start_response )
Nate,
John Chilton got that fixed for us. As you suggest, it involved a fix in our
proxy configuration.
JJ
On 2/1/12 9:01 AM, Nate Coraor wrote:
On Dec 19, 2011, at 12:24 PM, Jim Johnson wrote:
Hi,
I'm seeing the same behavior. Galaxy is returning a web page rather than the
requested
On Feb 1, 2012, at 10:05 AM, Jim Johnson wrote:
Nate,
John Chilton got that fixed for us. As you suggest, it involved a fix in
our proxy configuration.
JJ
Great, thanks!
--nate
On 2/1/12 9:01 AM, Nate Coraor wrote:
On Dec 19, 2011, at 12:24 PM, Jim Johnson wrote:
Hi,
I'm
On Jan 17, 2012, at 10:50 AM, Alexander Graf wrote:
Hi Nate,
sorry for my late reply, but I was on holiday last weeks.
I have looked in my apache error.log and access.log resulting into no new
insights - no output is given there.
So I gave nginx a try, getting the same error as before.
I
Hi,
I'm seeing the same behavior. Galaxy is returning a web page rather than the
requested .bai index file for the BAM file.
In class WebApplication ( lib/galaxy/web/framework/base.py ) in __call__( self,
environ, start_response ) line 133
# Setup the transaction
trans =
Hello,
I have recently updated our Galaxy dist and I'm running into problems
viewing BAM files in IGV (v2.0.22), saying: Invalid GZIP header.
I have configured the Apache as explained in the Wiki using this *http.conf*
:
