charset=UTF-8 not supported in content type

[GoogleCodeExporter]

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]

Thanks for providing this defect.  What server implementation does this occur 
in?

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

[GoogleCodeExporter]

It appends on jetty. 

Regards

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

[GoogleCodeExporter]

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]

Yes! 

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

[GoogleCodeExporter]

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

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

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:

• utf8.patch

[GoogleCodeExporter]

Thanks for the patch

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

[GoogleCodeExporter]

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

• Added labels: Milestone-1.3

[GoogleCodeExporter]

This issue was closed by revision r1282.

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

• Changed state: Fixed

[GoogleCodeExporter]

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

• Added labels: Release-1.3
• Removed labels: Milestone-1.3