Replay port specified is not used in Proxy mode

[machawk1]

% ipwb index samples/warcs/5mementos.warc | ipwb replay -P localhost:2005
Processing WARC records in 5mementos.warc complete
Proxying to localhost:2005
IPWB replay started on http://localhost:2016
 * Serving Flask app 'ipwb.replay' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off

The service is only accessible at port 2016. Is this expected behavior or in fact a bug, @ibnesayeed?

[machawk1]

ipwb/ipwb/replay.py

Lines 1049 to 1066 in 6ef47bc

	def start(cdxj_file_path, proxy=None):
	host_port = ipwb_utils.get_ipwb_replay_config()
	app.proxy = proxy
	if not host_port:
	ipwb_utils.set_ipwb_replay_config(IPWBREPLAY_HOST, IPWBREPLAY_PORT)
	# This will throw an exception if daemon is not available.
	ipwb_utils.check_daemon_is_alive()
	ipwb_utils.set_ipwb_replay_index_path(cdxj_file_path)
	app.cdxj_file_path = cdxj_file_path
	try:
	print((f'IPWB replay started on '
	f'http://{IPWBREPLAY_HOST}:{IPWBREPLAY_PORT}'))
	app.run(host='0.0.0.0', port=IPWBREPLAY_PORT)

sets the proxy variable but still starts ipwb on the predefined port.

[ibnesayeed]

This is the intended behavior, as long as Link header of mementos and TimeMaps have the proxy value in them. It will be the job of a reverse proxy to make the service running on a different port accessible the proxy URI.

[machawk1]

@ibnesayeed I figured this. Did we want to provide a way for the user that is running the replay service to specify a port beyond the ability to proxy?

[ibnesayeed]

The proxy flag is there to allow to run the service behind a reverse proxy or in a private network as app servers are not necessarily security hardened, so it is better to terminate TLS on a front server, deal with necessary loadbalancing, apply any firewalls, and only then forward the traffic to the app servers.

Honestly speaking, with many popular reverse proxy services we might not even need to explicitly know the front URI, instead, it can be identified implicitly from certain headers (provided, the reverse proxy server is setting those headers up, which, many do).

[machawk1]

@ibnesayeed Do we want to account for the scenario where one might want to simply run the localhost service in a port beyond we dictate (now 2016, prev. 5000)?

[ibnesayeed]

I thought we already allow customization of port number. If we do not then we should make it an option.

[machawk1]

@ibnesayeed Perhaps we do but there is not indication of it in the ipwb replay help:

[ibnesayeed]

Then we should add -p/--port option.

[machawk1]

@ibnesayeed Do you think that the custom port should be written to the ipwb config JSON?

• If yes, then subsequent runs of ipwb replay w/o the port specified will use the last custom port (instead of our default)
• If no, then the Link header for mementos still pulls from the config file and thus, will not reflect the custom port.

Which approach would you rather take?

[ibnesayeed]

I have my reservations about having a config file the way it is right now. That being said, of course we would want to reflect changes in that while we have it.

[machawk1]

@ibnesayeed
Ok, if we are going to write the custom port to the config file, if the custom port is not specified, should the default be written to the config file on subsequent startup when a custom port is not specified?

[machawk1]

Also, @ibnesayeed, if you have any suggestions on how a persistent configuration can be retained between runs, I am open to hear them.