Hi Dave,
The NoDecode flag did work for me. I added a note to the apache
configuration page of the galaxy wiki:
https://wiki.galaxyproject.org/Admin/Config/ApacheProxy
Thanks!
-Will
On Wed, May 11, 2016 at 10:23 AM, Dave Bouvier wrote:
> Will, Scott,
>
> You should be able to use the NoDecode
Will, Scott,
You should be able to use the NoDecode flag on the AllowEncodedSlashes
option without any problems. Galaxy will have decoded the slashes
internally by the time the request has reached the controller, and the
tool in question will be found.
-
Dave Bouvier
http://galaxyproject.org
Hello Scott,
Thanks for the helpful reply! Adding"AllowEncodedSlashes On" did allow me
to access the Data Manager tools. However, the Apache documentation has the
following note, "If encoded slashes are needed in path info, use of
NoDecode is strongly recommended as a security measure. Allowing sl
Hi Will,
We did manage to solve that problem by changing the Apache
configuration. We added "AllowEncodedSlashes On" to httpd.conf. I'm not
sure why the URL encoding changed, only that it did. See if that helps you.
Best,
Scott
On Tue, May 10, 2016 at 8:17 PM, Will Holtz wrote:
> Hi Scott,
>
Hi Scott,
I've recently hit the exact same problem. Have you had any success since
then with resolving this? I did some poking around and made a bit of
progress, but still no solution.
The Data Manager page under Run Data Manager Tools contains URLs like this:
https://galaxy.example.com/root?too
Hello,
I'm having an odd problem after updating to the latest version of Galaxy.
My users prepare data for analysis using data manager tools, such as
"data_manager_bwa_mem_index_builder". When an attempt is made to run one of
these tools, a pop up window opens stating "Tool request failed" and
und
