Allow non-standard URL base paths
damb opened this issue · 3 comments
Allow harvesting of routes including non-standard base FDSN URL paths i.e. base paths which do not fully match the pattern
/fdsnws/<service>/<majorversion>/
as specified by https://www.fdsn.org/webservices/FDSN-WS-Specification-Commonalities-1.2.pdf. As long as services implement FDSN webservice specifications apart from the URL base path both eidaws-federator
and eidaws-stationlite
should be able to cope with this particular minor deviation.
Note, for eidaws-federator
clients nothing changes since the service uses standardized FDSN base paths. Non-standard URL base paths are exclusively used internally.
Same for eidaws-wfcatalog
. See http://www.orfeus-eu.org/documents/WFCatalog_Specification-v0.22.pdf.
Recall, that this change requires verifying the service major version, beforehand (i.e. by means of the corresponding /version
resource). (Since the major version cannot be reliably determined from the URL base path, anymore.)
References: EIDA/userfeedback#80