[
http://jira.jboss.com/jira/browse/JBWS-1381?page=comments#action_12395375 ]
Remy Maucherat commented on JBWS-1381:
--------------------------------------
Sorry, I suppose I had missed this JIRA.
This configuration option is a behavior of the connector when it sends a response to a
specific user agent. As a result, it is not configured at the application level in Tomcat.
It seems if a user agent has HTTP/1.1 issues with webapp A, it could also have issues with
another webapp B, I think. restrictedUserAgents takes a regexp, and allows a fine match of
the problematic user agent. As a result, it should not needlessly degrade performance.
I don't understand the comment that this is not portable: this is an issue with a user
agent that is not HTTP/1.1 compliant, despite advertising otherwise. If a HTTP client
cannot handle chunking, it should consider making HTTP/1.0 requests instead (with
keepalive).
Disable HTTP chunking for J2ME client s
---------------------------------------
Key: JBWS-1381
URL:
http://jira.jboss.com/jira/browse/JBWS-1381
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Thomas Diesler
Assigned To: Remy Maucherat
Fix For: jbossws-native-2.0.4
How do I disable HTTP chunking for my EJB3 webservices?
I am using @WebMethod etc.
I need to disable HTTP chunking because my J2ME client (the wireless toolkit) can't
handle chunking yet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira