[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540675: marked as done (qa.debian.org: [PTS] SOAP: unicode data causes 500 Internal Server Error)

Your message dated Sat, 25 Jun 2011 08:56:05 +0200
with message-id <20110625065605.GA10517@rivendell.home.ouaza.com>
and subject line Re: Bug#630896: qa.debian.org: PTS SOAP interface always returns HTTP 500 Internal Server Error
has caused the Debian Bug report #630896,
regarding qa.debian.org: [PTS] SOAP: unicode data causes 500 Internal Server Error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

630896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630896
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: important

A query which needs to return unicode data isn't handled properly on the
SOAP server and returns a fault.  E.g., trying to show the maintainer
for drawterm, Martín Ferrari:

_________________________________ Sun Aug  9 11:38:06 2009 REQUEST:
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body><maintainer><source id="ob7e68ce0" xsi:type="xsd:string">drawterm</source></maintainer></SOAP-ENV:Body></SOAP-ENV:Envelope>
_________________________________ Sun Aug  9 11:38:06 2009 RESPONSE:
Internal Server Error
Date: Sun, 09 Aug 2009 15:38:06 GMT
Server: Apache
Content-Length: 939
Connection: close
Content-Type: text/xml; charset="utf-8"

<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Processing Failure</faultstring><detail><ZSI:FaultDetail><ZSI:string>
'ascii' codec can't encode character u'\xed' in position 4: ordinal not in range(128)</ZSI:string><ZSI:trace>/var/lib/python-support/python2.5/ZSI/dispatch.py:140:_Dispatch
Traceback (most recent call last):
  File "./bin/soap_query.py", line 46, in <module>
    print zsi_query(url, method, **args)
  File "./bin/soap_query.py", line 19, in zsi_query
    return getattr(ws, method)(**kwargs)
  File "/usr/lib/pymodules/python2.5/ZSI/client.py", line 78, in __call__
  File "/usr/lib/pymodules/python2.5/ZSI/client.py", line 191, in RPC
    return self.Receive(replytype, **kw)
  File "/usr/lib/pymodules/python2.5/ZSI/client.py", line 536, in Receive
    return _Binding.Receive(self, replytype, **kw)
  File "/usr/lib/pymodules/python2.5/ZSI/client.py", line 455, in Receive
    raise FaultException(msg)
ZSI.FaultException: Processing Failure
'ascii' codec can't encode character u'\xed' in position 4: ordinal not in range(128)
[trace: /var/lib/python-support/python2.5/ZSI/dispatch.py:140:_Dispatch

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message ---

On Tue, 21 Jun 2011, Alexandre Rossi wrote:
> So the way towards fixing this _particular_ issue seems to be, from what I
> understand, replacing the module xml.xpath (which does not exist anymore)
> usage with something.
> The attached patch seems to work on my squeeze box with my quick and dirty
> setup of the PTS SOAP interface. Watch for the extra python-lxml dependency.

Committed even if I can't test on the basis that things can't be worse
than not orking, it should be live already. Thanks for the patch!

Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)

--- End Message ---

Reply to: