search

acciduck / jscep

Automatically exported from code.google.com/p/jscep
MIT License
0 stars 0 forks source link

charset=UTF-8 not supported in content type #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

If charset=UTF-8 is append in content-type from scep server response (Content 
type:application/x-x509-ca-cert;charset=UTF-8)   then client throw an unknow 
content type exception.

I used 
ConcreteScepServlet exemple to reproduce it on jetty server.

Original issue reported on code.google.com by labor...@gmail.com on 28 Jun 2011 at 8:48

GoogleCodeExporter commented 8 years ago 
Thanks for providing this defect.  What server implementation does this occur 
in?

Original comment by davidgrant41 on 1 Jul 2011 at 9:45

GoogleCodeExporter commented 8 years ago 
It appends on jetty. 

Regards

Original comment by labor...@gmail.com on 6 Jul 2011 at 3:07

GoogleCodeExporter commented 8 years ago 
Do you mean that this is your own implementation, and that Jetty
appends the charset to your Content-Type header?

Original comment by da...@grant.org.uk on 6 Jul 2011 at 3:12

GoogleCodeExporter commented 8 years ago 
Yes!

Original comment by labor...@gmail.com on 6 Jul 2011 at 4:00

GoogleCodeExporter commented 8 years ago

Original comment by da...@grant.org.uk on 6 Jul 2011 at 5:59

GoogleCodeExporter commented 8 years ago 
Here is a patch that correct the issue. The issue was also reproduce on Tomcat 
6.

Regards

Original comment by labor...@gmail.com on 11 Jul 2011 at 12:37

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks for the patch

Original comment by da...@grant.org.uk on 12 Jul 2011 at 8:15

GoogleCodeExporter commented 8 years ago

Original comment by da...@grant.org.uk on 13 Jul 2011 at 6:46

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r1282.

Original comment by da...@grant.org.uk on 1 Aug 2011 at 6:55

GoogleCodeExporter commented 8 years ago

Original comment by da...@grant.org.uk on 21 Aug 2012 at 12:07