Charset utf 8 ошибка

I am trying to compile my .less document, and I am getting an error when trying to use @charset "UTF-8";.

I want to be sure my document is encoded correctly because of the way I embed my fonts. src: local(‘☺’), url(…);

Any ideas?

Update:

This seems to be a big, they say to fix it in the next version:

More Info:
https://less.tenderapp.com/discussions/problems/8-charset-error

Thanks for posting, this is fixed in
the upcoming 2.0 version, which should
be released sometime this month. It is
indeed due to @charset not being
parsed as a directive.

That comment by the LESS team was published on:

May 05, 2010 @ 05:50 AM

So it should be fixed in recent version. Make sure that you are using the latest version of it.

answered Jul 21, 2010 at 22:32

I have a problem with a WCF service.
I have a console application and I need to consume the service without using app.config, so I had to set the endpoint, etc. by code.
I do have a service reference to the svc, but I can’t use the app.config.
Here’s my code:

BasicHttpBinding binding = new BasicHttpBinding();

EndpointAddress address = new EndpointAddress("http://localhost:8731/WcfServicio/MiServicio");

MiServicioClient svc = new MiServicioClient(binding, address);
object ob = svc.PaisesObtener();

At the last line when I do svc.PaisesObtener() I get the error:

Content Type text/xml; charset=utf-8 was not supported by service
http://localhost:8731/WcfServicio/MiServicio.  The client and service bindings may be mismatched.

I saw this problem today when trying to create a WCF service proxy, both using VS2010 and svcutil.

Everything I’m doing is with basicHttpBinding (so no issue with wsHttpBinding).

For the first time in my recollection MSDN actually provided me with the solution, at the following link How to: Publish Metadata for a Service Using a Configuration File. The line I needed to change was inside the behavior element inside the MEX service behavior element inside my service app.config file. I changed it from

<serviceMetadata httpGetEnabled="true"/>  

to

<serviceMetadata httpGetEnabled="true" policyVersion="Policy15"/>

and like magic the error went away and I was able to create the service proxy. Note that there is a corresponding MSDN entry for using code instead of a config file: How to: Publish Metadata for a Service Using Code.

(Of course, Policy15 — how could I possibly have overlooked that???)

One more «gotcha»: my service needs to expose 3 different endpoints, each supporting a different contract. For each proxy that I needed to build, I had to comment out the other 2 endpoints, otherwise svcutil would complain that it could not resolve the base URL address.

answered May 5, 2016 at 13:51

I was also facing the same problem recently. after struggling a couple of hours,finally a solution came out by addition to

Factory="System.ServiceModel.Activation.WebServiceHostFactory"
to your SVC markup file. e.g.
ServiceHost Language="C#" Debug="true" Service="QuiznetOnline.Web.UI.WebServices.LogService" 
Factory="System.ServiceModel.Activation.WebServiceHostFactory" 

and now you can compile & run your application successfully.

Again, I stress that namespace, svc name and contract must be correctly specified in web.config file:

 <service name="NAMESPACE.SvcFileName">
    <endpoint contract="NAMESPACE.IContractName" />
  </service>

Example:

<service name="MyNameSpace.FileService">
<endpoint contract="MyNameSpace.IFileService" />
</service>

(Unrelevant tags ommited in these samples)

answered Oct 3, 2016 at 11:49

In my case, I had to specify messageEncoding to Mtom in app.config of the client application like that:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.1" />
    </startup>
    <system.serviceModel>
        <bindings>
            <basicHttpBinding>
                <binding name="IntegrationServiceSoap" messageEncoding="Mtom"/>
            </basicHttpBinding>
        </bindings>
        <client>
            <endpoint address="http://localhost:29495/IntegrationService.asmx"
                binding="basicHttpBinding" bindingConfiguration="IntegrationServiceSoap"
                contract="IntegrationService.IntegrationServiceSoap" name="IntegrationServiceSoap" />
        </client>
    </system.serviceModel>
</configuration>

Both my client and server use basicHttpBinding.
I hope this helps the others

answered May 23, 2018 at 7:14

I had this error and all the configurations mentioned above were correct however I was still getting «The client and service bindings may be mismatched» error.

What resolved my error, was matching the messageEncoding attribute values in the following node of service and client config files. They were different in mine, service was Text and client Mtom. Changing service to Mtom to match client’s, resolved the issue.

<configuration>
  <system.serviceModel>
      <bindings>
           <basicHttpBinding>
              <binding name="BasicHttpBinding_IMySevice" ... messageEncoding="Mtom">
              ...
              </binding>
           </basicHttpBinding>
      </bindings>
  </system.serviceModel>
</configuration>

answered Jun 29, 2020 at 9:58

I had this problem in .net 6.0

The problem was the Soap Version, the BasicHttpBinding targets Soap 1.1 by default, but the service uses Soap 1.2.

The solution was to create a custom binding that targets Soap 1.2:

private Binding GetBindingConfiguration()
{
    var textBindingElement = new TextMessageEncodingBindingElement()
    {
        MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
    };

    var httpsBindingElement = new HttpsTransportBindingElement()
    {
        MaxReceivedMessageSize = int.MaxValue,
        RequireClientCertificate = true //my service require certificate
    };

    return new CustomBinding(textBindingElement, httpsBindingElement);
}

var binding = GetBindingConfiguration();
var address = new EndpointAddress("https://nfe.sefa.pr.gov.br/nfe/NFeAutorizacao4"); //Brazil NF-e endpoint that I had to consume.

var svc = new MyService(binding, address);

//my service requires certificate
svc.ClientCredentials.ClientCertificate.Certificate = certificado; 

object ob = svc.PaisesObtener(); //call the method

answered Jan 23 at 20:30