cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "maomaode (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CXF-143) Content-Type not being set
Date Wed, 25 Oct 2006 08:17:23 GMT
     [ http://issues.apache.org/jira/browse/CXF-143?page=all ]

maomaode closed CXF-143.
------------------------

    Resolution: Fixed

> Content-Type not being set
> --------------------------
>
>                 Key: CXF-143
>                 URL: http://issues.apache.org/jira/browse/CXF-143
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.0-M1
>            Reporter: Daniel Kulp
>             Fix For: 2.0-M1
>
>
> The Content-Type header is not being set properly.    This might be an HTTP transport
issue instead.   Not sure.
> In anycase, the request messages are using the default:
> Content-type: application/x-www-form-urlencoded
> and the response messages are not setting ANY Content-type header.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message