Bug #40021 for SOAP-WSDL: charset: utf-8

Mon Oct 13 16:33:23 2008 ilgb [...] livius.net - Ticket created

Subject:

charset: utf-8

In SOAP::WSDL::Client and SOAP::WSDL::Transport::HTTP the charset generated is utf8 instead of utf-8, as it should be according to W3 site. This breaks access to AXIS web servces running on Tomcat, due to malformed 'content-type' header. Another bug is the duplication of charset=utf8 in the 'content-type' header. Regards, Liviu

Wed Oct 15 04:53:58 2008 martin.kutter [...] fen-net.de - Correspondence added

Subject:	Re: [rt.cpan.org #40021] charset: utf-8
Date:	Wed, 15 Oct 2008 10:53:37 +0200
To:	bug-SOAP-WSDL [...] rt.cpan.org
From:	Martin Kutter <martin.kutter [...] fen-net.de>

Hi Liviu, thanks for the report. Could you be a bit more specific about what is wrong and how it should be or provide an example? Thanks, Martin Am Montag, den 13.10.2008, 16:33 -0400 schrieb Liviu Ionescu via RT: Show quoted text

> Mon Oct 13 16:33:23 2008: Request 40021 was acted upon. > Transaction: Ticket created by ilg > Queue: SOAP-WSDL > Subject: charset: utf-8 > Broken in: 2.00.05 > Severity: Important > Owner: Nobody > Requestors: ilgb@livius.net > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=40021 > > > > In SOAP::WSDL::Client and SOAP::WSDL::Transport::HTTP the charset > generated is utf8 instead of utf-8, as it should be according to W3 > site. This breaks access to AXIS web servces running on Tomcat, due to > malformed 'content-type' header. > > Another bug is the duplication of charset=utf8 in the 'content-type' > header. > > Regards, > > Liviu > >

Wed Oct 15 04:54:00 2008 The RT System itself - Status changed from 'new' to 'open'

Wed Oct 15 05:03:55 2008 ilgb [...] livius.net - Correspondence added

Subject:	RE: [rt.cpan.org #40021] charset: utf-8
Date:	Wed, 15 Oct 2008 12:03:21 +0300
To:	<bug-SOAP-WSDL [...] rt.cpan.org>
From:	"Liviu Ionescu" <ilgb [...] livius.net>

Show quoted text

> thanks for the report. Could you be a bit more specific about > what is wrong and how it should be or provide an example?

in SOAP::WSDL::Transport::HTTP, when you create the 'content-type' request header for the http transactions, the correct syntax for the charset is 'utf-8', not 'utf8'. I noticed this on Tomcat, by enabling the dumpRequest Valve and checking the catalina.out log. if you'll do this, you'll also notice that charset=utf8 is writen twice in the content-type header. if you have further questions, don't hesitate to ask. regards, Liviu

Wed Oct 15 13:00:38 2008 martin.kutter [...] fen-net.de - Correspondence added

Subject:	RE: [rt.cpan.org #40021] charset: utf-8
Date:	Wed, 15 Oct 2008 18:59:22 +0200
To:	bug-SOAP-WSDL [...] rt.cpan.org
From:	Martin Kutter <martin.kutter [...] fen-net.de>

Hi Liviu, fixed in SVN. Thanks for reporting, Martin Am Mittwoch, den 15.10.2008, 05:03 -0400 schrieb Liviu Ionescu via RT: Show quoted text

> Queue: SOAP-WSDL > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=40021 > >

> > thanks for the report. Could you be a bit more specific about > > what is wrong and how it should be or provide an example?

> > in SOAP::WSDL::Transport::HTTP, when you create the 'content-type' request header for the http transactions, the correct syntax for the charset is 'utf-8', not 'utf8'. > > I noticed this on Tomcat, by enabling the dumpRequest Valve and checking the catalina.out log. > > if you'll do this, you'll also notice that charset=utf8 is writen twice in the content-type header. > > if you have further questions, don't hesitate to ask. > > regards, > > Liviu > > >

Wed Dec 03 17:44:31 2008 kutterma [...] users.sourceforge.net - Status changed from 'open' to 'resolved'