Skip to content

Remove the DODS legacy response headers from our responses #283

@ndp-opendap

Description

@ndp-opendap

Hyrax (the OLFS) sends back these old response headers from bacon the DODS days.

Do we need them?

Should we prune them?

Currently these headers are set as follows:

  • XDODS-Server: dods/3.2
  • XOPeNDAP-Server: asciival/, bes/, csv_handler/, dapreader_module/, dmrpp_module/, fileout_covjson/, fileout_json/, fileout_netcdf/, freeform_handler/, functions/, gateway/, hdf4_handler/, hdf5_handler/, libdap/, ncml_moddule/, netcdf_handler/, s3_reader/, usage/, w10n_handler/, xml_data_handler/
  • X-DAP: 3.2

And while these values are technically dynamic, they have not changed in years (maybe even decades)

The function that produces these headers is used 42 times in the code base:

    public static void setOpendapMimeHeaders(HttpServletRequest request, HttpServletResponse response)
            throws JDOMException, BadConfigurationException, PPTException, IOException, BESError {
        response.setHeader("XDODS-Server", getXDODSServerVersion(request));
        response.setHeader("XOPeNDAP-Server", getXOPeNDAPServerVersion(request));
        response.setHeader("X-DAP", getXDAPVersion(request));

    }

I say: Purge Them All!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions