Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: jabaws-ws
-
Labels:None
Description
Jalview's default JABAWS Service URL is http://www.compbio.dundee.ac.uk/jabaws .
A user has experienced problems accessing JABAWS (see https://discourse.jalview.org/t/alignment/2104 ), and whilst the reason has not yet been diagnosed one possibility might be a firewall against http.
Changing the Service URL from the default to https://www.compbio.dundee.ac.uk/jabaws and saying Yes to validation, results in an amber response, although most/all web services seem to be available.
However, using nettop on macOS (nettop -p PID_OF_JALVIEW) shows that when a web service is run, it is still using http on port 80, indicating that the web service entry points returned by JABAWS to Jalview were http.
It would be good if JABAWS contacted on https could return https web service URLs.
Given the relatively close timescale for Slivka services to be used, this would only be worth investigating if it took about 5 minutes to do!
A user has experienced problems accessing JABAWS (see https://discourse.jalview.org/t/alignment/2104 ), and whilst the reason has not yet been diagnosed one possibility might be a firewall against http.
Changing the Service URL from the default to https://www.compbio.dundee.ac.uk/jabaws and saying Yes to validation, results in an amber response, although most/all web services seem to be available.
However, using nettop on macOS (nettop -p PID_OF_JALVIEW) shows that when a web service is run, it is still using http on port 80, indicating that the web service entry points returned by JABAWS to Jalview were http.
It would be good if JABAWS contacted on https could return https web service URLs.
Given the relatively close timescale for Slivka services to be used, this would only be worth investigating if it took about 5 minutes to do!