> Some more 'stuff' to try!
>
> Let's see how it works ...
The secret-sauce recipe was:
in the mesh-ui config
apiUrl: '/mesh/api/v1/',
and in nginx
location ^~ /mesh/ {
...
proxy_pass http://meshproxy/;
proxy_redirect / /mesh/;
Hi,
> So you want the request to nginx of "/mesh/" to become a request to your
> upstream server of "/"?
Initially, that was the idea. For no reason OTHER than out of the box, the
upstream UI *is*, by default, available at
http://mesh.example.com:8080/
> It can be done; however, I suggest t
On Sun, Nov 11, 2018 at 03:55:06PM +, Moorage via nginx wrote:
Hi there,
> curl -i http://mesh.example.com:8080
> HTTP/1.1 302 Found
> Location: /mesh-ui/
> Content-Length: 0
>
> I want to expose that UI at an Nginx site custom path.
>
>
I have a simple nginx forward proxy, configured as:
server {
listen 8000;
resolver 8.8.8.8;
location / {
proxy_pass http://$host;
proxy_set_header Host $host;
}
}
The client behind its isp firewall sends the requ
I have a vhost running on nginx/1.15.6,
https://example.com
I have a standalone API service (fwiw, Gentics Mesh) running at
http://mesh.example.com
It exposes its UI, per its own config as
apiUrl: '/api/v1/',
Browsing to the direct link, Mesh responds as expected, corr
