Thanks,
I tried setting the "Connection: close" parameter on the client side for the
HTTP connection, but that didn't work because the WTK webservices don't have
any API to access the HttpConnection AFAIK
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986636#
[01:17:58] Thomas Diesler: so if the receiver cant handle it, it their problem?
[01:18:10] Jason Greene: yeah then they aren't HTTP/1.1 compliant
[01:18:20] Thomas Diesler: merci
[01:18:34] Jason Greene: in which case we can add them to the restricted agent
list
[01:18:36] ? in tomcat
[01:18:42] ?
Ah :)
Can I disable HTTP chunking?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983447#3983447
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983447
___
jboss-user mailing
| Transfer-Encoding: chunked
|
This is a normal HTTP chunked message. The message is split into multiple
chunks, each chunk starts with the length in hex, followed by the data. The end
is signified by a 0 length chunk.
-Jason
View the original post :
http://www.jboss.com/index.html?mod
I installed a pipeline between the client and server which shows the problem:
POST /seems-ejb/SeemsServiceImpl HTTP/1.1
User-Agent: Profile/MIDP-1.0 Configuration/CLDC-1.0
Content-Language: en-US
Content-Type: text/xml
SOAPAction: "
User-Agent: UNTRUSTED/1.0
Content-Length: 325
Host: geoffreydeskt
