So.. is the problem related to the fact that the CISCO IOS does not recognize the Content-Type: or more on the CISCO side (so that we have to send 'Content-type' instead of 'Content-Type') ?
One small note: it seems that the patch you sent is related to the 'Content-Length:' header instead... Anyhow, I am working on the 2.0 version of the server, which is quite different. Still, there's a lot of work to do, but it will use LibPKI so it will be easy to integrate with PKCS#11 devices.. something that many people wanted!!! :D Alpha testers are welcome... Cheers, Max On 05/18/2010 05:36 PM, Joachim Astel wrote:
Greetings openca-ocspd users,
I've recognized a problem with Cisco and newer IOS versions
together with OCSPD-1.5.1-rc1.
OCSPD parses the HTML header against:
Content-Type:
^ with a uppercase 'T'
But Cisco routers would need:
Content-type:
^ with a lowercase 't'
I would suggest to fix this before release of OCSP-1.5.1-final.
As a "quick hack", I developed the following patch which recognizes both of
the above formats -- in fact, to be fully RFC conformant, you would need a
'strnstr' function call matching any upper and lower case scenarios:
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
