Green release - target loader mixing http and https URLS requests

[Waztom]

Loading a target correctly calls via https URL for one of the apo structures but via http for another.

• https correctly requested for Mpro-x2097 (standard dataset naming convention) =>

GET | https://fragalysis.xchem.diamond.ac.uk/media/target_loader_data/0575688f-6d02-4961-b459-eb07ebd3d395/Mpro-2023-11-13/Mpro/upload_1/aligned_files/Mpro-x2097/Mpro-x2097_A_1001_Mpro-J0071%2BB%2B501_apo.pdb

• http incorrectly requested for Mpro-J0013. @kaliif is this the .pdb generated via XChem Align/Conor's code? The J-naming convention does not match our usual x2097 for example. The difference in naming convention could be a hint as to why this is happening @boriskovar-m2ms naming convention this might be helpful for you to debug frontend as well =>

GET | http://fragalysis.xchem.diamond.ac.uk/media/target_loader_data/0575688f-6d02-4961-b459-eb07ebd3d395/Mpro-2023-11-13/Mpro/upload_1/aligned_files/Mpro-J0013/Mpro-J0013_A_501_Mpro-J0071%2BB%2B501_apo.pdb

[kaliif]

Fixed in backend release 2.0.4

[Waztom]

@kaliif is this fix in staging yet - I see staging is tagged as 2.0.4, but has it been deployed?

I still get failed http GET requests when clicking on P (side chains), C (interactions) and S (surface) for the LHS datasets.

[kaliif]

@Waztom it's deployed, yes. Do you have the request that isn't working? I've been clicking around and it seems to work for me.

[Waztom]

@kaliif in Firefox, I get a bunch of http requests for GET example:

GET | http://fragalysis.xchem.diamond.ac.uk/media/target_loader_data/296b06a4-6c13-45d3-9963-d04af737ec7b/XX01ZVNS2B-v1/XX01ZVNS2B/upload_1/aligned_files/XX01ZVNS2B-x0089/XX01ZVNS2B-x0089_B_301_XX01ZVNS2B-x0709%2BB%2B301_apo.pdb

[boriskovar-m2ms]

Doesn't work for me either (in Chrome).

[kaliif]

@Waztom @boriskovar-m2ms fixed in 2.0.7