Re: Problem with chunked encoding

[email protected] Wed, 2 Apr 2003 16:05:28 +0200
Newsgroups gmane.comp.java.enhydra.ksoap
Message-ID <[email protected]>
Hi,

If you have a problem regarding chunked encoding then you may try, as a 
workaround, to force your client to use HTTP 1.0 (instead of 1.1) so that 
the server will not respond using chunked encoding.

Regards,

----------------------------------------------------------------------------
Sebastien Petrucci
Java Technology Consultant - Altran Europe
Philips Remote Control Systems
Interleuvenlaan 74-76, B-3001 Leuven (Belgium)
M +32(0)497502521    T  +32(0)16394 598
----------------------------------------------------------------------------









José María del Álamo <[email protected]>
Sent by: 
[email protected]
2003-04-01 17:18
Please respond to ksoap

 
        To:     <[email protected]>
        cc:     (bcc: Sebastien Petrucci/LEU/COMP/PHILIPS)
        Subject:        Ksoap:  Problem with chunked encoding
        Classification: 



Hi Stefan. Thanks for the previous response.
I tried to replace the version I was using (Wireless Toolkit 1.0.3) for 
the latest one (Wireless Toolkit 2.0). Results: Nothing at all, the 
problem persists. I'm using jdk1.4 (SE) and when I test my program (The 
call to the Web Service) in a PC client, it works. This is the trace i get 
when i try to execute the program (in the emulator):
 
org.kxml.io.ParseException: unexpected: ParseEvent type=128 text='0204' 
@-1:-1
        at org.kxml.parser.AbstractXmlParser.read(+53)
        at org.ksoap.SoapEnvelope.parseHead(+19)
        at org.ksoap.SoapEnvelope.parse(+5)
        at org.ksoap.transport.HttpTransport.call(+372)
        at org.ksoap.transport.HttpTransport.call(+12)
        at es.dit.upm.composs.mobile.SelectorServicio.enviarMensaje(+38)
        at es.dit.upm.composs.mobile.SelectorServicio.commandAction(+33)
        at 
javax.microedition.lcdui.Display$DisplayAccessor.commandAction(+152)
        at com.sun.kvem.midp.lcdui.EmulEventHandler$EventLoop.run(+427)
So it seems the problem doesn't come from ksoap nor Kxml. I do not know 
what any more i can test. It could be a problem with the HTTP version 
(1.0)? I think no, but i do not know how to go on.
 
Any idea will be a great advance.
 
Chema.