Legacy HTTPS Only Configuration - Revision history

Drn@ecs.soton.ac.uk at 09:07, 20 May 2022

2022-05-20T09:07:04Z

Drn@ecs.soton.ac.uk: Added full instructions, potential issues and side effects.

2022-05-20T09:06:32Z

Added full instructions, potential issues and side effects.

Drn@ecs.soton.ac.uk: Drn@ecs.soton.ac.uk moved page Legacy HTTPS Configuration to Legacy HTTPS Only Configuration: More appropriate title

2022-05-20T08:46:29Z

Drn@ecs.soton.ac.uk moved page Legacy HTTPS Configuration to Legacy HTTPS Only Configuration: More appropriate title

Drn@ecs.soton.ac.uk: Added placeholder

2022-05-20T08:15:40Z

Added placeholder

New page

This is a temporary placeholder, whilst the configuration for this is tested.

@@ Line 7: / Line 7: @@
   </Location>
 Substitute <tt>example.eprints.org</tt> with the hostname for your EPrints repository.
 . Run the following command to regenerate the Apache webserver configuration for your EPrints repository:
   EPRINTS_PATH/bin/generate_apacheconf --system --replace
 . Reload the Apache webserver:
   apachectl graceful
 . Test that you web browser now automatically redirects by going to the HTTP page (e.g. http://example.eprints.org/view/)
@@ Line 18: / Line 21: @@
 == Potential Issues ==
 . If you change you primary hostname (i.e. what is set in <tt>$c->{host}</tt> in your archive's <tt>cfg/cfg.d/10_core.pl</tt> you will need to make sure you update <tt>apachevhost.conf</tt> as well.
 . If you already have a complex <tt>apachevhost.conf</tt> the configuration you need to add may not be compatible.  In theory you should be able to strip out all configuration in this file and just replace it with the configuration in step one of the above instructions.  However, there may be scenarios where this would not be appropriate.  So take care in any changes you make.

← Older revision		Revision as of 09:06, 20 May 2022
Line 1:		Line 1:
−	This is a ~~temporary placeholder, whilst~~ the configuration for this ~~is tested~~.	+	'''These instructions on this page assume that [[HTTPS]] configuration is already deployed on your EPrints repository. This is how you can deploy HTTPS only configuration with HTTP to HTTPS redirects of EPrints repositories earlier that version 3.4.1.'''
		+
		+	== Instructions ==
		+	1. Create a file under the <tt>cfg/</tt> directory of you archive called <tt>apachevhost.conf</tt> (i.e. <tt>EPRINTS_PATH/archives/ARCHIVEID/cfg/apachevhost.conf</tt>) If it already exists at the following configuration at the top of the file.
		+	<Location />
		+	Redirect / https://example.eprints.org/
		+	</Location>
		+	Substitute <tt>example.eprints.org</tt> with the hostname for your EPrints repository.
		+
		+	2. Run the following command to regenerate the Apache webserver configuration for your EPrints repository:
		+	EPRINTS_PATH/bin/generate_apacheconf --system --replace
		+
		+	3. Reload the Apache webserver:
		+	apachectl graceful
		+
		+	4. Test that you web browser now automatically redirects by going to the HTTP page (e.g. http://example.eprints.org/view/)
		+
		+	== Potential Issues ==
		+	1. If you change you primary hostname (i.e. what is set in <tt>$c->{host}</tt> in your archive's <tt>cfg/cfg.d/10_core.pl</tt> you will need to make sure you update <tt>apachevhost.conf</tt> as well.
		+
		+	2. If you already have a complex <tt>apachevhost.conf</tt> the configuration you need to add may not be compatible. In theory you should be able to strip out all configuration in this file and just replace it with the configuration in step one of the above instructions. However, there may be scenarios where this would not be appropriate. So take care in any changes you make.
		+
		+	== Side effects of switching to HTTPS only ===
		+	[Simplified_HTTPS_Configuration#Issues_and_Troubleshooting\|Here] are some of the potential side effects you may face if you are switching your EPrints repository to HTTPS only (with HTTP to HTTPS redirects. If you are creating a new repository that will start out being HTTPS only, all these side-effects should be negated.

← Older revision	Revision as of 08:46, 20 May 2022
(No difference)