RE: GET, conneg, and a media type parameter

The accept header field and the use of content negotiation is optional
in HTTP. A client is free to use it but we can't require it.

Henrik

>I don't understand. Can you please describe the point of 
>departure from HTTP semantics? HTTP says you should use an 
>accept header to say what kind of representation you want 
>back. If you know you want a SOAP-envelope back, why not ask for it?
>
>Henrik Frystyk Nielsen wrote:
>> 
>> That would be wrong as it would require that SOAP changed HTTP 
>> semantics
>> - a point we have worked hard not to do.
>> 
>> Henrik
>> 
>> >Can the "accept" header be made a mandatory part of SOAP over HTTP 
>> >messages so that clients can rely upon it? In a sense, it could be 
>> >used as a simpler, more predictable form of the old 
>SOAPAction...and 
>> >of course for regular HTTP content negotation.
>