Galaxy stable image 20.09 resolving to wrong GALAXY_URL

1

Hi there,

I am trying to integrate galaxy docker image on my platform and I am having issues with how galaxy docker image resolves GALAXY_URL.

The thing is next:
When we make request to the galaxy, request flows through few proxies, and the last one, let’s call it Proxy Z is on another domain, let’s call it z.proxy.com. Galaxy container is running behind that proxy, thus GALAXY_URL is pointing to z.proxy.com
I would like to know if it’s possible to configure GALAXY_URL to point to our organizational public domain, instead of the proxy’s.

We are using at the moment latest stable galaxy docker image 20.09 Docker running 20.09 galaxy version

2

Hi @heisenberg

Does this documentation help? #Galaxy-behind-proxy

If not, please consider asking a question at the dedicated chat bgruening/docker-galaxy-stable - Gitter. You can include a link to this thread in your post for context. One item to clarify is the goal a bit more – do you want to change the base URL that users see/access or the underlying API configuration? I’m guessing the first but please confirm.

3

Hi @jennaj

I’ve already checked the documentation and there’s nothing about how GALAXY_URL variable is resolved. This is the variable that is used for generating response links in Get Data section, and it’s also used when fetching welcome page.

for ex. this is where GALAXY_URL is used, when openning UCSC Archaea table browser in Get Data section:

Screenshot 2022-12-16 at 11.43.38
Screenshot 2022-12-16 at 11.43.381920×1014 212 KB

I’ll write in chat you’ve provided, thanks!

1 Like
4

heya, adding some info to this:

it looks like GALAXY_URL is built from the request’s HOST header field; if i change my etc/hosts file and navigate to galaxy with the added host, then use the UCSC Get Data tool, the request looks like:

GET
scheme: http
host: somedomain.bork:8080 <==== my addition to /etc/hosts
filename: /tool_runner/data_source_redirect
tool_id: ucsc_table_direct_archaea1
Address: 127.0.0.1:8080

…and the response looks like:

HTTP/1.1 302 Found
Server: nginx/1.14.0 (Ubuntu)
Date: Wed, 04 Jan 2023 21:31:38 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 591
Connection: keep-alive
x-frame-options: SAMEORIGIN
Location: http://archaea.ucsc.edu/cgi-bin/hgTables?GALAXY_URL=http%3A//somedomain.bork%3A8080/tool_runner&tool_id=ucsc_table_direct_archaea1&sendToGalaxy=1&hgta_compressType=none&hgta_outputType=bed

(note the GALAXY_URL=http%3A//somedomain.bork%3A8080/)

are you navigating from the desired URL in your browser, but getting the downstream proxy URL when redirected?

here’s some more random info in case it’s useful:

using the ‘Get Data → UCSC Archaea table browser’ follows this link:

  • $URL/tool_runner/data_source_redirect?tool_id=ucsc_table_direct_archaea1

…which uses this chunk of logic to check the galaxy tool:

regards,

  • Luke
2 Likes