Editing Simplified HTTPS Configuration (section)

=== EPrint URI Change ===
When an EPrint made live it will acquire a URI in the form

 <nowiki>http://example.eprints.org/eprint/id/1234</nowiki>

If you switch over to [[Simplified_HTTPS_Configuration#HTTPS_Only | HTTPS Only]] the above URI will be updated (if you refresh abstracts) to

 <nowiki>https://example.eprints.org/eprint/id/1234</nowiki>

For most repositories this will not be an issue but if your repository is harvested by a third party application, it may rely on the URI as a unique identifier and if this changes it may that all the EPrints are new as none of the URIs are the same as before.

For third party applications that integrate through the [http://bazaar.eprints.org Bazaar] (EThoS, PIRUS, Symplectic Repository Tools, etc.) no problems relating to this have been identified.  However, if your repository has a bespoke third party application this may be affected and is something you should test beforehand if possible but as soon as you go live with the new configuration otherwise.

If you need to ensure your EPrint URIs do not change you can add the <code>uri_url</code> configuration option at the end of your archive's <code>10_core.pl</code> configuration as follows:

 $c->{uri_url} = "http://" . $c->{securehost};

OAI-PMH (e.g. <nowiki>http://example.eprints.org/cgi/oai2</nowiki> and <nowiki>https://example.eprints.org/cgi/oai2</nowiki>) provide different relations (http or https) for a publication but the OAI identifier is protocol independent and therefore stays the same.  Therefore, third party applications that make use of OAI-PMH should not be affected if they harvest as the protocol specifies.