Base url as parameter

[glaroc]

Hi, we are in a situation where we would like to run the stac-fastapi in a virtual machine behind a proxy server. In other words, the uri in the request parameters that the app sees are not the uri that the end user sees, so the urls shown in the catalogue are wrong. Is there a way to set the base url from an environmental variable or through a parameter ? We are currently deploying from docker-compose.

[glaroc]

If anyone is facing the same issue, we dealt with it through our nginx reverse proxy.

   location /stac-fast-api/ {
        proxy_http_version  1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header Host $host/stac-fast-api;
        proxy_pass http://stac-api-app:8082/;
    }

Importantly, the following environment variable must be set, here in the docker-compose file:

      - FORWARDED_ALLOW_IPS=*

[vincentsarago]

maybe this can help developmentseed/titiler#345 (comment)

[glaroc]

@vincentsarago this is the same solution we ended up using. Thank you.

[gnosys-ccoupal]

I'm having a similar issue trying to access stac-fastapi behind AWS API Gateway. I can get through to the stac api on my EC2 instance, but all links included in the response have the EC2 DNS name, not the advertised API gateway domain name.

Based on above, my docker container has the environment variable FORWARDED_ALLOW_IPS=* (didn't change behaviour). I also added proxy_headers=True to uvicorn.run (required?) as below:

        uvicorn.run(
            "stac_fastapi.sqlalchemy.app:app",
            host=settings.app_host,
            port=settings.app_port,
            log_level="info",
            reload=settings.reload,
            proxy_headers=True,
        )

But this didn't change behaviours either. Any ideas is welcome.

[geospatial-jeff]

#415 added support for forwarding headers