Hello Sir, It seems that the content-type "application/timestamp-response" is an editorial errata. The corrected is "application/timestamp-reply".
Please see the following: http://www.rfc-editor.org/errata_list.php Regards, Koichi Sugimoto. 2011/5/13 Stefano Ravaioli via RT <[email protected]>: > Hi, we are using the tsget command found in openssl-1.0.0d for RFC3161 > timestamp requests. > > We found that it was not working with one of our provider "www.infocert.it" > because they add to the content-type of the response the suggested filename, > as in: > > Content-Type: application/timestamp-response; name="1234567890.tsr" > > so tsget exits with an error because it looks for an exact match with > "application/timestamp-response" or "application/timestamp-reply". > > I just changed the match so that it looks for the presence of one of the two > content-types. > > if (lc($ct) !~ /application\/timestamp-reply/ > && lc($ct) !~ /application\/timestamp-response/) { > $error_string = "unexpected content type returned: $ct"; > } # RST 20110511, InfoCert sends the suggested file name for the > response after the content-type > > Look for the string "RST", or use diff ;-) > > Best regards, > > > Stefano Ravaioli - CINECA > - http://www.cineca.it/ - > - tel. +39 051 6171 597 - > > > > > > > > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
