Operating behind a reverse proxy

andrewgdotcom · October 23, 2017, 3:54pm

Hi, all.

I’m trying to run dremio behind a reverse proxy so that, e.g. ‘https://site.example.com/dremio/’ is proxied to the dremio listening port. The problem arises because dremio assumes that all internal links start with ‘/’, and I can find no way to reconfigure the application root URL.

Does this configuration feature exist? If not, I will have to resort to some hacky HTML rewriting in the reverse proxy…

Thanks,
Andrew.

chris · October 25, 2017, 10:15pm

Hi @andrewgdotcom, there currently isn’t a config option for this.
Supporting proxy situations like this one isn’t currently on our roadmap, but I’m going to start tracking it internally.

In the meantime, we do accept open source contributions if you are interested. Just off the top of my head, our webpack and api constants file are probably good starting points:

github.com

dremio/dremio-oss/blob/master/dac/ui/webpack.config.js

/*
 * Copyright (C) 2017 Dremio Corporation
 *
 * Licensed under the Apache License, Version 2.0 (the 'License');
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

const fs = require('fs');
const path = require('path');
const childProcess = require('child_process');
const webpack = require('webpack');

This file has been truncated. show original

github.com

dremio/dremio-oss/blob/master/dac/ui/src/constants/Api.js

/*
 * Copyright (C) 2017 Dremio Corporation
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
const host = window.location.host;
const isSecure = window.location.protocol === 'https:';

export const API_URL = `//${host}/apiv1`;
export const API_URL_V2 = `//${host}/apiv2`;

This file has been truncated. show original

(Though I’d be remiss not to mention that there are security implications to such a configuration, and would be happy to discuss further should you want more information about that.)

ajsalow · October 17, 2022, 12:46am

Hi, I’m curious if this is possible now when installing with the v2 helm chart? Would like to host like https://site.example.com/dremio/. The main issue now is after the initial http request additional files are requested like https://site.example.com/vendor.16085bdce08fdfffd92c.js instead of https://site.example.com/dremio/vendor.16085bdce08fdfffd92c.js

Topic		Replies	Views
Building dremio with proxysettings in maven settings.xml	0	1285	October 24, 2018
Serve Dremio UI and API under given path	2	1097	November 24, 2021
Changing value for DREMIO_ORIGIN/ WebUI not loading	1	1338	July 9, 2020
Proxy for socket connection	0	869	August 5, 2020
Dremio S3 ignores nonProxyHosts settings	1	1023	April 14, 2023

Operating behind a reverse proxy

Related topics