[CXF-2690] Oneway MEP with fastInfoset without 'force' results in no compression

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.2.6
• Fix Version/s: Invalid
• Component/s: OtherDatabindings, Transports

Environment

Windows Vista
jdk1.6.0_07

• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Reinis Vicups
• Created: 04/Mar/10 09:09
• Updated: 01/Apr/10 08:17
• Resolved: 11/Mar/10 16:20

Description

If a fastInfoset (accept=application/fastinfoset) @Oneway Message is sent to the Server and 'force' option of the fastInfoset is not set to 'true', the server would give 202 response and would use content-type: text/xml like this:

15:04:33,000 DEBUG [main] cxf.transport.http.HTTPConduit (2132) - Header fields:
null: [HTTP/1.1 202 Accepted]
Content-Length: [0]
Content-Type: [text/xml]
Server: [Jetty(6.1.21)]

I am not sure if this is the consequence of server answering with text/xml, but as a result the client issues all of the following requests with text/xml aswell instead of switching to application/fastinfoset.

Per definition fastinfoset works like this:
1. client requests server with content-type:text/xml but indicates that it (client) accept:application/fastinfoset;
2. server responds with content-type:application/fastinfoset
3. all the following requests from client to server will be with content-type:application/fastinfoset

Additional info that might be relevant:

• I have tested with multiple messages (not just two)
• All messages were sent from the same instance of client and received by the same instance of server (no new instances were created)