Loading README.md +4 −3 Original line number Diff line number Diff line Loading @@ -33,13 +33,14 @@ The above configuration example assumes: `ID=ivo://<authority>/<resource-key>?<relative-pathname>#extnum` The service decodes IVOID part after question mark '?'. The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. '/srv/ska/surveys'). The service decodes IVOID part after the question mark '?'. The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. `/srv/ska/surveys`). The FITS extension number `#extnum` is optional. Default is the primary HDU. Note that the service appends '**soda**' to ACCESS_CONTEXT_ROOT. Data access example: A data access example: ```bash curl -s -k --get --data-urlencode "ID=ivo://some-auth/some-key?some/path/somefile.fits" Loading Loading
README.md +4 −3 Original line number Diff line number Diff line Loading @@ -33,13 +33,14 @@ The above configuration example assumes: `ID=ivo://<authority>/<resource-key>?<relative-pathname>#extnum` The service decodes IVOID part after question mark '?'. The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. '/srv/ska/surveys'). The service decodes IVOID part after the question mark '?'. The pathname in the ID is relative to the path in compose.yaml volume-mapping (e.g. `/srv/ska/surveys`). The FITS extension number `#extnum` is optional. Default is the primary HDU. Note that the service appends '**soda**' to ACCESS_CONTEXT_ROOT. Data access example: A data access example: ```bash curl -s -k --get --data-urlencode "ID=ivo://some-auth/some-key?some/path/somefile.fits" Loading
