The behaviour of apps/tsget is technically RFC 3161-compliant, but some TSAs return responses based on a typo in the RFC, namely:
3.4. Time-Stamp Protocol via HTTP ... Two MIME objects are specified as follows. Content-Type: application/timestamp-query ... Content-Type: application/timestamp-reply ... Upon receiving a valid request, the server MUST respond with either a valid response with content type application/timestamp-response or with an HTTP error. The tsget utility should probably accept the spurious application/timestamp-response mimetype (perhaps in its accept-header, but definitely in its internal validity check of the response) to ensure acceptance of replies received from TSAs which use the timestamp-response header rather than the timestamp-reply header. (I've found at least two TSAs which return the spurious header, but I don't have the names with me now.) ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
