On 21/09/2017 10:52, Mungo Carstairs (Staff) wrote: Not sure if this will have an impact on Jalview. Probably not at all, if our requests do not have a referer domain of www.ebi.ac.uk<http://www.ebi.ac.uk>. not absolutely sure what you mean there.. Currently PDBFTSRestClient.PDB_SEARCH_ENDPOINT = "http://www.ebi.ac.uk/pdbe/search/pdb/select?";<http://www.ebi.ac.uk/pdbe/search/pdb/select?>; I tried changing this to https and it worked fine. The site has a QuoVadis certificate which I guess should be trusted by all users. I suggest we change this constant to https for the next release. Yes. 2.10.2b1 could also be patched right now. I'm less sure of how Jalview's (Jersey WebResource.accept()) code would handle a 302 redirect, if that is what happens on 1st October. Googling suggests some people have had trouble with this, even after setting a config property FOLLOW_REDIRECTS. I would expect this is a common issue (if it really is one) - perhaps check for updates to Jersey ? Also, we need to test the other clients in Jalview - particularly for our own services. The plan is to apply redirects for www.compbio.dundee.ac.uk<http://www.compbio.dundee.ac.uk>, and ideally also *.jalview.org (we already have this for issues and wiki, and source (ish), but also need to do it for www.jalview.org<http://www.jalview.org>). Could you ask Fabio about getting a test jabaws service set up under https with a redirect on http to see what happens with the Jabaws client ? Thanks, Jim The University of Dundee is a registered Scottish Charity, No: SC015096
_______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
