Talk:XDAP header

How to implement the 3.2 behavior

The BES writes out the XDAP: header using functions in the (mis-named) cgi_util.cc file. Those functions are called by DODSFilter and the BES uses an instance of DODSFilter as its BESTransmitterFilter. (There are similar looking functions in BESUtil.cc (i.e., functions with the same names as the functions in cgi_util.cc) but they are not used for the DAP responses.)

The functions in cgi_util.cc use a compile-time constant to get the value of the XDAP: header.

To implement the 3.2 feature, our code will need to pass the value of the XDAP-Accept: header to libdap and libdap will need to pass the value of the XDAP: header back when it returns the response object.

We might think about adding a RequestResponse object to libdap to hold information about the request and resulting response that is used for bookkeeping (like the protocol version number). Or we could add this information in fields of DapObj...