Remove hardcoded `LDR` URL prefix from client calls
This client currently automatically prefixes all URL paths with /LDR
as a convention held over from the old server infrastructure. However, as described in &4, the server doesn't actually know about that path, since it's a <Location
at the web server layer. So, the client shouldn't really presume that this is part of the path.
My recommendation is to
- reconfigure the client to continue to automatically prepend API paths with
/LDR
but to detect and replace/LDR/LDR
- then once that is deployed, ask administrators to set the
GWDATAFIND_SERVER
variable to include the/LDR
path prefix, e.g.GWDATAFIND_SERVER="datafind.ldas.cit:80/LDR"
- then after a while, reconfigure the client properly to not automatically prepent API paths with
/LDR
This will then allow the server administrators to not have to continually configure the datafind server to appear at the /LDR
location, and the client to better support the versioned APIs now supported by the new server, see #28.