Do you have any question about this error?
Message type: E = Error
Message class: SECATT_HTTP_STATUS - eCATT HTTP Status Messages
Message number: 410
Message text: Perdido: El recurso solicitado ya no está en el servidor
The requested resource is no longer available at the server and no
forwarding address is known. This condition is expected to be considered
permanent. Clients with link editing capabilities SHOULD delete
references to the Request-URI after user approval. If the server does
not know, or has no facility to determine, whether or not the condition
is permanent, the status code 404 (Not Found) SHOULD be used instead.
This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web
maintenance by notifying the recipient that the resource is
intentionally unavailable and that the server owners desire that remote
links to that resource be removed. Such an event is common for
limited-time, promotional services and for resources belonging to
individuals no longer working at the server's site. It is not necessary
to mark all permanently unavailable resources as "gone" or to keep the
mark for any length of time -- that is left to the discretion of the
server owner.
El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
SECATT_HTTP_STATUS410
- Perdido: El recurso solicitado ya no está en el servidor ?Get instant SAP help. Start your 7-day free trial now.
SECATT_HTTP_STATUS409
No es posible cerrar la pregunta (conflicto con status actual de recurso)
¿Qué causa este problema? The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in...
SECATT_HTTP_STATUS408
Timeout de petición
¿Qué causa este problema? The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the requ...
SECATT_HTTP_STATUS411
El servidor rechaza tratamiento sin longitud contenido parám.definida
¿Qué causa este problema? The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds ...
SECATT_HTTP_STATUS412
Requisito previo fallido
¿Qué causa este problema? The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. T...
Haga clic en este enlace para buscar todos los mensajes de SAP.