[EP-tech] Re: EPrints behind a reverse proxy

Ian Stuart Ian.Stuart at ed.ac.uk
Mon Feb 27 12:32:57 GMT 2012

On 27/02/12 12:07, raffaele messuti wrote:
> still not convinced , but i'll try ;)
> the parameters entered in epadmin create (hostname and port) are
> written in 10_core.pl
> where is the magic in changing it later? they are written elsewhere?

The "change it back" part is under "Configuring the repository"

The way a reverse-proxy works is thus:

1) Request comes in for host1.example.com
2) Proxy translates the address to services.example.com:1234
3) Backend server does whatever it needs to do & writes the page (to the 
proxy server)
4) Proxy server takes the response, and replaces the address line from 
services.example.com:1234 to host1.example.com (but leaves the content 
as is)
5) Proxy server returns the data to the client

So - why the two-step install?
1) When you install the server initially, you need to build it against 
its native interface, so services.example.com:1234
2) When you use in public, you need all the in-page URLs to refer to the 
public name (host1.example.com)

Try it....


Ian Stuart.
Developer: Open Access Repository Junction and OpenDepot.org
Bibliographics and Multimedia Service Delivery team,
The University of Edinburgh.


This email was sent via the University of Edinburgh.

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

More information about the Eprints-tech mailing list