[Archivesspace_Users_Group] Path issue with Archivesspace and reverse proxy

[Blake Carver]

Hi Lyman,
I have that bug reported in here:
https://archivesspace.atlassian.net/browse/AR-1566

I found the same thing that you did, running under a prefix (in your case /archivesspace/public/) causes some path issues. I never did find a fix, but did find that switching to running the site as 2 subdomains worked just fine. 

Blake Carver
   Systems Administrator LYRASIS
   blake.carver at lyrasis.org
 



________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Lyman Ross <lross at uvm.edu>
Sent: Thursday, March 30, 2017 11:47 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Path issue with Archivesspace and  reverse proxy

We recently migrated our Archivist Toolkit database to Archivesspace and have upgraded to 1.5.4. We’re hoping to provide access via nginx and reverse proxy. The public interface is mapped to /archivesspace/public/. Everything seems to be working with the exception of component links which are missing the prefix and showing as relative paths off the webroot. I’m hoping this is a simple configuration issue. Does anyone know which configuration variable controls these links?

Lyman Ross
Systems Librarian
University of Vermont Libraries

lross at uvm.edu
(802) 656-4508