Any Content-Type attribute is interpreted as "charset"

          WL 6.1 sp 2
          I have a servlet that set the Content-Type of the response to something like "application/*;name=blabla".
          According to the http/1.1 spec that should be fine.
          However, WL seems to interpret any Content-Type attribute as if it were "charset".
          In the example the attribute is "name" and the result is an exception saying that
          the encoding "blabla" cannot be found and the default encoding will be used.
          Is that a (known) bug?
          Here is a stack trace:
          <05.06.2002 13:18:24 CEST> <Error> <HTTP> <[WebAppServletContext(7200375,myWebApp,/myWebApp)]
          Unsupported encoding: "null" specified. Using the default encoding.
          java.io.UnsupportedEncodingException: "blabla.txt"
          at sun.io.Converters.getConverterClass(Converters.java:107)
          at sun.io.Converters.newConverter(Converters.java:138)
          at sun.io.CharToByteConverter.getConverter(CharToByteConverter.java:67)
          at weblogic.servlet.internal.ChunkOutput.create(ChunkOutput.java:99)
          at weblogic.servlet.internal.ChunkOutputWrapper.changeToCharset(ChunkOutputWrapper.java:46)
          at weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:734)
          at weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:581)
          at weblogic.servlet.internal.ServletResponseImpl.setContentType(ServletResponseImpl.java:248)
          at com.bla.MyServlet.handleFileDownLoad(MyServlet.java:219)

This has been fixed for 610sp3 already. One off patches are available for
          610sp1 and 610sp2.
          Contact support if you need one. CR061782 was used to track the CR.
          --Vinod.
          "Dimitri I. Rakitine" <[email protected]> wrote in message
          news:[email protected]...
          > Yup, it looks like a bug, but, thankfully, it appears that WebLogic just
          prints out
          > the exception stacktrace and doesn't consider this as an error - client
          still gets
          > back the correct response:
          >
          >
          > HTTP/1.0 200 OK
          > Date: Thu, 06 Jun 2002 18:47:49 GMT
          > Server: WebLogic WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
          > Content-Length: 7569
          > Content-Type: application/*;name=blabla
          > ...
          >
          > Alexander Bunkenburg <[email protected]> wrote:
          >
          > > WL 6.1 sp 2
          >
          > > I have a servlet that set the Content-Type of the response to something
          like "application/*;name=blabla".
          > > According to the http/1.1 spec that should be fine.
          >
          > > However, WL seems to interpret any Content-Type attribute as if it were
          "charset".
          > > In the example the attribute is "name" and the result is an exception
          saying that
          > > the encoding "blabla" cannot be found and the default encoding will be
          used.
          >
          > > Is that a (known) bug?
          >
          >
          > > Here is a stack trace:
          >
          > > <05.06.2002 13:18:24 CEST> <Error> <HTTP>
          <[WebAppServletContext(7200375,myWebApp,/myWebApp)]
          > > Unsupported encoding: "null" specified. Using the default encoding.
          > > java.io.UnsupportedEncodingException: "blabla.txt"
          > > at sun.io.Converters.getConverterClass(Converters.java:107)
          > > at sun.io.Converters.newConverter(Converters.java:138)
          > > at
          sun.io.CharToByteConverter.getConverter(CharToByteConverter.java:67)
          > > at
          weblogic.servlet.internal.ChunkOutput.create(ChunkOutput.java:99)
          > > at
          weblogic.servlet.internal.ChunkOutputWrapper.changeToCharset(ChunkOutputWrap
          per.java:46)
          > > at
          weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImp
          l.java:734)
          > > at
          weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.
          java:581)
          > > at
          weblogic.servlet.internal.ServletResponseImpl.setContentType(ServletResponse
          Impl.java:248)
          > > at com.bla.MyServlet.handleFileDownLoad(MyServlet.java:219)
          >
          > --
          > Dimitri
          >

Similar Messages

Content type attribute

how do i add attribute to a MimeMessage object's content-type?
when i create a MimeMessage I always get a content-type which looks similar below,
Content-Type: multipart/related;
boundary="----=_Part_1_2704014.1032764882171"
now i want to add a "type=application/smil" attribute like below
Content-Type: multipart/related;
boundary="----=_Part_1_2704014.1032764882171";type=application/smil
i cant find a MimeMessage or Multipart function that enables me to add an attribute to the content-type? what's the work around here??
thanks!

Your question:
now i want to add a "type=application/smil" attribute like below
Content-Type: multipart/related;
boundary="----=_Part_1_2704014.1032764882171";type=application/smil
i cant find a MimeMessage or Multipart function that enables me to add an attribute to the content-type? what's the work around here??
thanks!
Did you ever find a solution to this?
thanks, brian

OSB defaulting Content-Type to "multipart/related" in case of attachments

I have scenario where I need to invoke a REST Webservice from OSB which accepts only media types which has "multipart/atom+xml". OSB is used for protocol transformation converting the SOAP request into the HTTP POST request with multipart. I have Proxy Service which will unwrap the message from the SOAP Body and post the same message into the payload of the Business Service and the attachment is passed 'as is' from the SOAP Service. The external REST Service Provider expects the media type to be "multipart/atom+xml", but in OSB when an attachment is present in the message, OSB is overrding the "Content-Type" proeprty to "multipart/related" inspite of me setting the "Content-Type" property of HTTP Transport Header in OSB and as result external RESTFUL Service is throwing "415-Unsupported Media Type" error. Below is the test results. One interesting thing is, it happens only when there is attachment present in the message. In case of a message which doesn't have attachment any "Content-Type" specified in the Transport Header is passed by the OSB to the external service. Any help is highly appreciated.
OSB Transport Header
Added the header <http:Content-Type>multipart/atom+xml</http:Content-Type>
Actual Raw Message
POST http://xxx7200:7004/XXXInterfaces/identify HTTP/1.1
Content-Type: multipart/related; type="text/plain"; start="<Root_-328322390>"; boundary=MIME_Boundary; charset=UTF-8
MIME-Version: 1.0
User-Agent: Java1.6.0_17
Host: xxx7200:7004
Accept: text/html, image/gif, image/jpeg, */*; q=.2
Proxy-Connection: Keep-Alive
Content-Length: 4823
Expected Raw Message
POST http://xxx7200:7004/XXXInterfaces/identify HTTP/1.1
Content-Type: multipart/atom+xml; boundary=MIME_Boundary;
User-Agent: Java1.6.0_17
Host: xxx7200:7004
Accept: text/html, image/gif, image/jpeg, */*; q=.2
Proxy-Connection: Keep-Alive
Content-Length: 4803
-KC
Edited by: 799459 on Apr 8, 2011 5:36 AM
Edited by: 799459 on Apr 8, 2011 7:02 AM
Edited by: 799459 on Apr 8, 2011 7:13 AM
Edited by: 799459 on Apr 8, 2011 7:14 AM

HTTP content-type header has the following limitation as per osb doc.
Oracle Service Bus run time may overwrite these headers in the binding layer when preparing the message for dispatch. If these headers are modified, $inbound and $outbound are updated accordingly. So what you are seeing may be working as designed. Cant the remote service accept the multi part related content type set up by osb ?

Multiple "Workflow Task (SharePoint 2013)" content type found

Users on one specific sub-site reported that they are unable to add site columns to content type. When user clicks "add existing site column" user get error message - upon looking up on ULS, it indicate there were duplicate column "System.ArgumentException:
No two choices should have the same ID". I came across similar issue on different site before and resolved it by deleting duplicate column, plus that site column was not used on any list or associated with any content type but this time duplicate
column is "Task outcome" column which is associated with "Workflow Task(SharePoint2013)" content type. So looking up these two specific site column and content type I noticed there are 8 occurrence of each at affected site
level (see below on image).
Similarly there are 8 "Task Outcome" columns under Site Columns. So I refreshed staging env with prod copy and tried to delete "Workflow Task(SharePoint 2013" content type and got error message as shown below. Under Site features, I noticed
"SharePoint 2013 Task List" feature was enabled, hoping this will do the trick I disabled it as we still use SharePoint 2010 workflows, but to no avail.
Sorry, something went wrong
The content type "Workflow Task (SharePoint 2013)" is part of an application feature.
Not sure how it got started and something will try to find out but any advise on how to fix this issue?
Thanks,
MK Sin

Hi Sin,
According to your description, my understanding is that the users got an error when clicking “add existing site column”.
For deleting the duplicate “Task outcome”column, you need to go to the “Workflow Task(SharePoint 2013)” content type, click the “Task outcome” column, and remove it from the content type.
Then go to site columns, find the duplicate columns, and delete them and make sure only one “Task outcome” column exists.
After the above, re-add the “Task outcome” into the “Workflow Task(SharePoint 2013)” content type.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect

Hi Experts,
I am facing with the flowing error when we are receiving for the soap receiver chanel.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
is their any content type to give in soap receiver channel.
please let me know.
Regards
Raju

I think the message is misleading. HTTP 302 meaning is that the url specified in not found or invalid for that service. You might want to check with external system that the specified URL in the SOAP receiver communication channel is right? Also you can find the URL from the WSDL itself. Similar test do it outside PI using the SOAPUI or XMLSPY and see the response error.

Content Type settings inside a sub-site are going to be ignored, and it will use the parent content type settings

I have an enterprise site collection with the following content type settings inside the list content type (columns such as security, document type, etc as required):-
Then I have created a new sub-site of type enterprise wiki, the default list content type for the subsite will look as follow which have the columns such as security, document type as optional :-
But now if I went to the sub-site and I chose to create a new page, and i leave all the columns empty, then the system will raise an error that the columns such as; security, document type, etc are required. although inside the sub-site content type the
columns are defined as optional. So seems that the wiki page inside the sub-site is referencing the parent content type and not its own sub-site content type.
Can anyone advice on this please ?

Hi John,
I tested the same scenario per your post, however the columns retained the same settings in sub-site in the same content type.
I recommend to verify the things below:
Was the content type you used for creating the page the one created in the parent site?
Did you create another content type in sub-site based on the one created in parent site? I recommend to click the column name to go inside the column settings and then check if the Optional is selected. If yes,
change it and click OK, then change it back to Optional again to see if the issue still occurs.
Best regards.
Thanks
Victoria Xia
TechNet Community Support
1. no
2. no. i did not create any content type. i have just create a new subsite of type enterprise wiki , and the content type settings will be same as the parent content type, which have all these columns set as optional. but seems these settings will be ignored
as these columns will raise an error if i leave them empty. so seems that the subsite's library will use the same settings as its parent site collection library, which have these columns set as required...
so i have the following , to make things clearer:-
1. inside the site collection , the content type at the site collection level have these columns as optional.
2. inside the site collection's library the list content type copy, have these columns as required.
3. on the subsite list content type copy, i have these columns as optional. but these columns on the subsite library will be treated as required columns ...

Setting webservice response content type / charset header

I have a webservice .war file.
I need to set the content-type/charset http header and add another http header. I wrote a filter to do that and had partial success. The other header (pics-label) is indeed sent in the response with the correct value. However, setting the content type proved to be another matter.
I read through the documentation that one can set the system property weblogic.webservice.i18n.charset=utf-8. However, this doesn't seem to work. The filter setting the header also doesn't work. It seems that weblogic has the final word on that. Only when I set the <web-service> element attribute charset="UTF-8" does the header gets back to the client.
Due to deployment/build related issues which I won't get into, this is most annoying.
If anyone has encountered a similiar issue and have a solution/workaround/thoughts I'll be glad to hear about it.
P.S.
Also tried -Dfile.encoding=UTF-8 but didn't do any good.
Thanks.

you don't define a charset for non-text file types. Excel files are not text files.

Content-Type=application/x-www-form-urlencoded with UTF-8 data which servlet fails to interpret correctly .

My Environment is Weblogic 6.1 SP2 on WIN2K.
I have an HTTP client sending an HTTP request with
Content-Type=application/x-www-form-urlencoded
the data in HTTP request is in UTF-8. Note that HTTP client does not specify charset=UTF-8
as part of the Content-Type.
I have a servlet "VosXmlEvents" processing this HTTP request.
The HTTP request contains data like “Zoë” which the servlet below
interprets as “ZoÃ«” causing me to think that my deployment settings
might be wrong.
My Deployment settings:
In weblogic.xml deployment descriptor I have specified following:
<charset-params>

<input-charset>
<resource-path>/vos/events/xml/*</resource-path>

<java-charset-name>UTF8</java-charset-name>
</input-charset>

<charset-mapping>
<iana-charset-name>ISO_8859-1:1987</iana-charset-name>
<java-charset-name>ISO-8859-1</java-charset-name>
</charset-mapping>
<charset-mapping>
<iana-charset-name>ISO_8859-1:1987</iana-charset-name>
<java-charset-name>ISO8859_1</java-charset-name>
</charset-mapping>
<charset-mapping>
<iana-charset-name>UTF-8</iana-charset-name>
<java-charset-name>UTF-8</java-charset-name>
</charset-mapping>
<charset-mapping>
<iana-charset-name>UTF-8</iana-charset-name>
<java-charset-name>UTF8</java-charset-name>
</charset-mapping>
</charset-params>
My web.xml has:
<servlet>
<servlet-name>VosXmlEvents</servlet-name>
<servlet-class>some class name</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>VosXmlEvents</servlet-name>
<url-pattern>/vos/events/xml/*</url-pattern>
</servlet-mapping>
According to Servlet spec. 2.3 sec. SRV.4.9 Request data encoding, cut pasting
from spec below:
"Currently, many browsers do not send a char encoding qualifier with the Content-Type
header, leaving open the determination of the character encoding for reading HTTP
requests. The default encoding of a request the container uses to create the request
reader and parse POST data must be “ISO-8859-1”, if none has been
specified by the client request. However, in order to indicate to the developer
in this case the failure of the client to send a character encoding, the container
returns null from the getCharacterEncoding method.
If the client hasn’t set character encoding and the request data is encoded
with a different encoding than the default as described above, breakage can occur.
To remedy this situation, a new method setCharacterEncoding(String enc) has been
added to the ServletRequest interface. Developers can override the
character encoding supplied by the container by calling this method. It must be
called prior to parsing any post data or reading any input from the request. Calling
this method once data has been read will not affect the encoding."
Q1. Should not <input-charset> related settings in weblogic.xml for a servlet
helps container actually do some thing like setCharacterEncoding(String enc) on
HTTP Request before it call the servlet?
Q2. If not then that would mean I have to programatically call setCharacterEncoding(String
enc)to correctly interpret my HTTP Request?
Q3. If the answer to Q1 is "yes" then I will assume that getInputStream() or getReader()
methods on the HttpServletRequest will give the chacter in the client encoded
format which in this case is UTF-8, i.e I will get "Zoë" as in this example. Am
I correct here?
Reference:
1. http://edocs.bea.com/wls/docs70/webapp/components.html#139932
2. http://java.sun.com/j2se/1.3/docs/guide/intl/encoding.doc.html

Stefan,
Thanks for the information. I have the following question then.
The Webserver I am interacting with does not recognize user and password provided in the channel. It accepts user and pwd in payload and in application/x-www-form-urlencoded content type only.
Sample Raw Post that server server requires looks like this
User=yourname&Password=yourpassword&INPUT_XML=%3C%3Fxmlversion%3D%221.0%22standalone%3D%22no%22%3F%3E%3CDELIVERY%3E%3CMESSAGE%3E%0D%0A++++%3CDESTINATION_ADDR%3E%2B447900570205%3C%2FDESTINATION_ADDR%3E%%3C%2FMESSAGE%3E%0D%0A%0D%0A%3C%2FDELIVERY%3E%
What i have done is that constructed the post manually in Java code in un encoded form and expected the HTTP Adapter to do the encoding. Having done this, the HTTP Server is able to scuccessfully parse the xml except for & and < , > chars which err out as invalid XML.
Is there an elegant way of doing above scenario using XML post and standard HTTP Adapter.
Best Regards,
Sudharshan N A

The Content-type charset issue

Hi
I've been reading the thread about the origins of the #HEAD# substitition: Where does #HEAD# substitution comes from?
Because I want to change the charset parameter in the content-type meta tag in my application. I'm a bit worried since it appears that the value of this attribute is controlled by the PlsqlNLSLanguage setting in the dad. OK and Jan has had various settings here. But there are references to documentation that state that from Apex 3.0 you really can't change the setting with regards to charset (http://download-uk.oracle.com/docs/cd/B32472_01/doc/relnotes.300/b32465/toc.htm#BGBCJIEA) - it must be AL32UTF8.
Now, I'm on 2.2, but I'm definately planning on upgrading at some point, so I guess that limitation will apply to my config too.
AL32UTF8 yields a content type meta tag with charset=utf-8. If I can't change that, how do I get charset=iso-8859-1 like I need?
Scott proposed to put in a second content-type meta tag to (maybe) override the one that Apex makes. I'm going to try that to see if it saves me. But can it be true that Apex doesn't give me any options here - other than relying on browsers probably guessing what I want when I give them HTML-hacks? In my view, that would clearly constitute a bug.
Jakob

Hi Joel
Thanks for your reply. You're right. It's clearly not a bug after all. But you might want to slap Scott for suggesting what he did in Where does #HEAD# substitution comes from? :-)
I understand that the problem lies with the XmlHttpRequest so it's not Apex' fault.
My issue arises when people post non-ascii (Danish) characters in forms. Æ, Ø, Å etc. The browser encodes these as UTF-8 and they become garbage to the database - or to be more precise, they look like two or three bytes of even stranger characters when I retrieve them from the database. Also when I retrieve them with Apex and put them back into the very same input element that they came from.
Personally I can't think of a good reason why the conversion seems to happen OK when I get the values back in the browser (if it didn't the funky characters would be "right" when viewed in the browser) and not happen when I post? I realize that I should be careful with the b-word, but the marshalling is not symmetric so some component in here doesn't behave ... reasonably. Perhaps it's the browser...
Would you or anybody know of a workaround? Others must have had this problem? Is it possible to tweek the form or the form elements (using attributes like enctype, accept, accept-charsest with which I must admin I have no previous experience)? Or will I have to do some really nasty hacking in either JavaScript or database triggers or something?
The Apex report on NLS in the database contains this:
NLS_CHARACTERSET     WE8MSWIN1252
NLS_COMP     BINARY
NLS_LANGUAGE     DANISH
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_NCHAR_CONV_EXCP     FALSE
NLS_NUMERIC_CHARACTERS     ,.
NLS_SORT     DANISH
NLS_TERRITORY     DENMARK
I don't believe that I'm free to change any of that. There are other applications running against the database.
Jakob

Sharepoint error - Search Issue - The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1).

i see this error everywhere - In ULS logs, on site. On the site > Site settings > search keywords; I see this -
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>IIS 7.0 Detailed Error - 500.19 - Internal Server Error</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 40px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px; border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696; border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;'.
I am facing issues in searching, my managed metadata service is not running, search results page throws internal error. Any Idea why this above error comes.
P.S: We use windows authentication in our environment.

Hi IMSunny,
It seems you have solved this issue based on your another post.
http://social.technet.microsoft.com/Forums/en-US/aa468ab0-1242-4ba8-97ea-1a3eb0c525c0/search-results-page-throws-internal-server-error?forum=sharepointgeneralprevious
Thanks
Daniel Yang
TechNet Community Support

Error consuming Web service - content type text/xml;charset=utf-8 of the response message does not match the content type of the binding

Hi all,
We are trying to interact with Documentum server through DFS exposed WCF which communicates through port 9443 and we are provided with documentum issued Public Key certificates. We have successfully imported the certificates in client machine and configured
the bindings as below in our .Net web application config file.
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
Also, we set the message encoding as MTOM and the wcf client object initialization code snippet is as below,
ObjectServicePortClient
serviceClient = new
ObjectServicePortClient(new
WSHttpBinding("ObjectServicePortBinding1"),
new
EndpointAddress(UriUtil.ObjectServiceUri));
if (serviceClient.Endpoint.Binding
is
WSHttpBinding)
   WSHttpBinding
wsBinding = serviceClient.Endpoint.Binding as
WSHttpBinding;
wsBinding.MessageEncoding =
"MTOM".Equals(transferMode) ?
WSMessageEncoding.Mtom :
WSMessageEncoding.Text;
serviceClient.Endpoint.Behaviors.Add(new
ServiceContextBehavior(Config.RepositoryName,
Config.DocumentumUserName,
Config.DocumentumPassword));
When we execute the above code, we are getting error message as below,
Exception: The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported
method is implemented properly. The first 407 bytes of the response were: '<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:VersionMismatch</faultcode><faultstring>Couldn't
create SOAP message. Expecting Envelope in namespace http://schemas.xmlsoap.org/soap/envelope/, but got http://www.w3.org/2003/05/soap-envelope </faultstring></S:Fault></S:Body></S:Envelope>'
Then, we changed the bindings as below
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="
Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
We are getting another error message,
Exception: The client certificate is not provided. Specify a client certificate in ClientCredentials.
Any pointers on resolving this issue would be highly helpful.
Thanks

Hi Dhanasegaran,
As per your case, the corresponding details which may guide you to resolve this issue:
1. First of all, you can try to call the wcf service directly from the browser & check where it will point out the correct location.
2. In config file ,Set IncludeExceptionDetailInFaults to true to enable exception information to flow to clients for debugging purposes .
Set this to true only during development to troubleshoot a service like below :
<serviceBehaviors>
<behavior name="metadataAndDebugEnabled">
    <serviceDebug
      includeExceptionDetailInFaults="true"
/>
    <serviceMetadata
      httpGetEnabled="true"
      httpGetUrl=""
/>
</behavior>
</serviceBehaviors>
3. I suggest you to change that <security mode ="TransportWithMessageCredential"> instead of <security mode ="Transport">
for more information, refer the following link :
https://msdn.microsoft.com/en-us/library/aa354508(v=vs.110).aspx

WCF returning "The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)"

I have a WCF service I am trying to run on a new installation of 64-bit Windows Server 2008 IIS. Although it runs fine on Windows 2003 IIS, it is throwing the error in the thread title, which appears to be a server config issue, but I am not sure. Googling and searching the MSDN forums did not turn up a solution. I tried running WCF Logging, but that didn't help either.
Does anyone have any suggestions on how to solve this probelm?
Here is the error:
The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>500 - Internal server error.</title>
<style type="text/css">

I have the same issue on Windows 7 machine. The service works fine using a SoapUI client but a .Net client faisl to get a response.
Hi,
I have a WCF service which works perfectly when using SoapUI but throws error in my .Net client.
{"The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first
1024 bytes of the response were: '<HTML><HEAD><link rel=\"alternate\" type=\"text/xml\" href=\"http://xyz.mysite.com/ysa/Broker.svc?disco\"/><STYLE type=\"text/css\">#content{ FONT-SIZE: 0.7em;
PADDING-BOTTOM: 2em; MARGIN-LEFT: 30px}BODY{MARGIN-TOP: 0px; MARGIN-LEFT: 0px; COLOR: #000000; FONT-FAMILY: Verdana; BACKGROUND-COLOR: white}P{MARGIN-TOP: 0px; MARGIN-BOTTOM: 12px; COLOR: #000000; FONT-FAMILY: Verdana}PRE{BORDER-RIGHT: #f0f0e0 1px solid; PADDING-RIGHT:
5px; BORDER-TOP: #f0f0e0 1px solid; MARGIN-TOP: -5px; PADDING-LEFT: 5px; FONT-SIZE: 1.2em; PADDING-BOTTOM: 5px; BORDER-LEFT: #f0f0e0 1px solid; PADDING-TOP: 5px; BORDER-BOTTOM: #f0f0e0 1px solid; FONT-FAMILY: Courier New; BACKGROUND-COLOR: #e5e5cc}.heading1{MARGIN-TOP:
0px; PADDING-LEFT: 15px; FONT-WEIGHT: normal; FONT-SIZE: 26px; MARGIN-BOTTOM: 0px; PADDING-BOTTOM: 3px; MARGIN-LEFT: -30px; WIDTH: 100%; COLOR: #ffffff; PADDING-TOP: 10px; FONT-FAMILY: Tahoma; BACKGROUND-COLOR: #003366}.intro{MARGIN-LEFT: -15px}</STYLE><TITLE>Broker
Service</TITLE></HEAD><BODY><DIV id=\"content\"><P class=\"head'."}
I have the same service hosted on my local machine and when I point to the local service I can execute the operation with no issues. The message encoding is Soap11. I tried changing to Soap12 but I get exact same error. Any ideas greatly appreciated.
I do have windows Activation Features installed and I am using .Net Framework 4.
Thanks
Sofia Khatoon

Tomcat always generates charset in Content-Type http header !!!

Dear All! I need urgent help with a problem I met with and any suggestion are very appreciated!
The problem is:
We are using Tomcat as a web server (and JSP engine), and we would like to use a user control written in C# 2.0 on one of our pages. I've developed such component and tested it using JBuilderX (in fact it resides inside a JSP page). Everything is working fine while debugging using JBuilder, but when I tried to deploy the solution - I got a problem, my dll was not downloaded properly. Let me illustrate this with a test example. I wrote a test html page:
<html > <head> <title>Test</title> </head> <body> <object id="MyControl" height="300" width="550" classid="http://localhost:8080/MyDLL.dll#WindowsControlLibrary1.UserControl1"> </object> </body> </html>
When I tried to open it I did not get my control loaded. I check the headers of the server http response and found that Tomcat added the following string as
Content-Type: application/x-msdownload;charset=ISO-8859-1
I'm positive that in this case Content-Type should look like
Content-Type: application/x-msdownload
(or application/octet-stream if I would choose to define mime type for dll in server's web.xml as
<mime-mapping> <extension>dll</extension> <mime-type>application/octet-stream</mime-type> </mime-mapping>
- it does not matter as I understand )
so Content-Type should not contain any charset for DLL part of response. NO charset=ISO-8859-1 !!
But Tomcat adds it. :-( And I don't know how to prevent him doing that.
On the other hand when I tried to open this page using Tomcat started from within JBuilder (port number in this case is different) - then everything was going good and control was downloaded to "Temporary Internet Files" and shown on the page.
Content-Type field in this case was:
Content-Type: application/x-msdownload
without any charset.
So, my question is: How to suppress Tomcat wish to add the "charset=ISO-8859-1" string to the Content-Type http response header?
What should I do to load my test html page succesfully?
Thanks in advance for you time and patience!
Sincerely yours, Igor

Back to the top

Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text

Hi I am in trouble with JAX-WS 2.1.2M1
I try to call my Webservice like this:
Service service = Service.create(serviceName);
        service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, "http://spblue.liberty:8084/SPBlue/GlobalLogoutService");
Dispatch<SOAPMessage> disp = service.createDispatch(portName, SOAPMessage.class, Service.Mode.MESSAGE);
        SOAPMessage message = XmlUtil.getSOAPMessageFromString(request);
        SOAPMessage response = disp.invoke(message);when my disp invokes I get following Exception which seems to as a little Problem, anyway I don�t know how to get rid of this Exception.
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:116)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
at com.sun.xml.ws.client.Stub.process(Stub.java:234)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:166)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:192)
at test.service.Logout.requestLogout(Logout.java:115)
at test.service.Logout.main(Logout.java:149)
ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
JDWP exit error AGENT_ERROR_NO_JNI_ENV(183): [../../../src/share/back/util.c:820]
my ServiceClass is:
@ServiceMode(value=Service.Mode.MESSAGE)
@WebServiceProvider( targetNamespace="http://spblue.liberty:8084/wsdl/globalLogout")
public class GlobalLogoutServiceImpl implements Provider<SOAPMessage> {
     * Web service operation
    public SOAPMessage invoke( SOAPMessage logoutRequest ){
        return logoutRequest;
}So how can I set the Charachter set before invokikng the service.
Or how can I change the Service to accept UTF-8.
Well, I don�t know.
Any help is welcome.

Hi,
I don't know if this can help you, but I had a similar problem while invoking a web service. Eventually, I found out that the server was returning an html error page, and not the expected xml answer.
That's why the client code raises such an error... It means that the MIME type of the anser is text/html (for the html page) and not the text/xml type of the 'nominal' web service answer.
You can verify this by using a proxy to intercept the http request and answer involved in this web service invocation (use Fiddler for instance). Then, you will see that the server responds by sending an html page saying that something is wrong.
Hope this helps...
Sam

"Content-type: text/html; charset=utf-8 cache-control: no-cache..." display

"Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "
is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
Does anyone have any tips on how I would go about finding something like this?
The page was using a custom theme but that stopped working when we upgraded to 4.1. So, I copied the Simple Green template to start modifying.
Mentioning that in case it's relevant...
Thanks!

LauraC wrote:
"Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "Looks like an HTTP header...
is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
Does anyone have any tips on how I would go about finding something like this?If it's included within the <tt>body</tt> element in the original page source then it's produced by something in APEX and the position in the source will give a clue as to where. You should also run the page in Debug mode and look at the trace to see if there's any clues there.
If it's visible in the generated page source but not the original then it's produced by something dynamic in the page. Possibly some JS lingering from the previous theme?

Any Content-Type attribute is interpreted as "charset"

Similar Messages

Maybe you are looking for