Software Open Access
Nathan Potter; The Robot Travis; James Gallagher; Uday Kari; Slav Korolev; ideaesb; Riley Rimer; Kodi Neumiller; Sam Lloyd
In order to make the server's behavior more understandable to users, and its configuration more understandable to admins we have changed the way that the server responds to client requests for the unadorned Dataset URL and the way that the server generates Data Request Form links in its catalog pages. There are new configuration parameters to control these behaviors.
This configuration parameter has been DEPRECATED - Use the
<DatasetUrlResponse /> and
<DataRequestForm /> elements to configure this behavior (see below).
<DatasetUrlResponse type="..." />
The DatasetUrlResponse element is used to configure the type of response that the server will generate when a client attempts to access the unadorned Dataset URL. The type of response is controlled by the value of the type attribute.
<DataRequestForm type="..." />
The DataRequestForm element defines the target DAP data model for the dataset links in the "blue-bar" catalog.html pages. These links point to the DAP Data Request Form for each dataset. This element also determines the type of Data request form page returned when the DatasetUrlResponse type="requestForm" and the request is for the Dataset URL. Allowed type values are: dap2 and dap4.
<DataRequestForm type="dap4" />
When enabled users will be able to use Hyrax as a file server and download the underlying data files/granules/objects directly, without utilizing the DAP APIs.
<!--AllowDirectDataSourceAccess / -->
The presence of this element will cause the Data Request Form interfaces to "force" the dataset URL to HTTPS. This is useful for situations where the sever is sitting behind a connection management tool (like AWS CloudFront) whose outward facing connections are HTTPS but Hyrax is not using HTTPS. Thus the internal URLs being received by Hyrax are on HTTP. When these URLs are exposed via the Data Request Forms they can cause some client's to have issues with session dropping because the protocols are not consistent.
<!-- ForceDataRequestFormLinkToHttps / -->