10 messages in org.apache.ws.axis-devRe: [AXIS2] Proposal to implement htt...
FromSent OnAttachments
keith chapmanOct 16, 2007 10:17 pm 
Paul FremantleOct 17, 2007 12:05 am 
Sanjiva WeerawaranaOct 17, 2007 8:13 pm 
Glen DanielsOct 18, 2007 3:41 am 
keith chapmanOct 18, 2007 5:37 am 
Nicholas L GallardoOct 18, 2007 2:14 pm.gif, .gif, .gif
keith chapmanOct 18, 2007 6:53 pm.gif, .gif
Sanjiva WeerawaranaOct 19, 2007 5:27 am 
keith chapmanOct 21, 2007 12:51 am 
keith chapmanNov 20, 2007 10:24 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [AXIS2] Proposal to implement http content negotiationActions...
From:Paul Fremantle (pzf@gmail.com)
Date:Oct 17, 2007 12:05:07 am
List:org.apache.ws.axis-dev

Keith

I agree that if I do a GET I want to get back plain ole XML and not SOAP1.1. Since the model you are proposing also supports GET returning SOAP 1.2 (with the appropriate Accept header), I think this works just fine.

+1

Paul

On 10/17/07, keith chapman <keit@gmail.com> wrote:

Hi Devs,

There have been some thought on http content negotiation. With the concept of builders and formatters we have now this could be implemented trivially. The idea is to use the "Accept" http header to serve the response requested by the client. While going through this though I came across a issue though. This occurs when a request is sent via a GET using a browser (Cause the browser automatically adds the Accept http header). The Accept header sent by firefox is "Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9 ,text/plain;q=0.8,image/png,*/*;q=0.5". The confusion comes in because text/xml is used for both SOAP and REST responses.

I believe having http content negotiation as a feature will be a nice addition to Axis2. And I propose that we treat text/xml as a REST response in implementing this. This would mean that you cannot ask for a SOAP 1.1response
uaing http content negotiation (A SOAP 1.1 response will be went only when the request is SOAP 1.1 and there is no matching value in the Accept header).

What do u think? Should we go ahead and implement this proposal?

-- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org pa@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com