Updating site content type failed

The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.

The set presented MAY be a subset or superset of the original version.

For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server.

The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent.

This class of status code indicates that the client's request was successfully received, understood, and accepted. The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server.

The request has been fulfilled and resulted in a new resource being created.

Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response.

(For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) The client SHOULD continue with its request.

Search for updating site content type failed:

updating site content type failed-2updating site content type failed-59

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating site content type failed”