ich wollte mal für meine Mobilfunkbox ein neuen Spruch aufsprechen, dabei weis ich aber nicht ganz welcher Error dafür richtig ist (siehe zB http://www.w3.org/Protocols/HTTP/1.1/sp ... atus-Codes).
An sich war die erste Überlegung, es muss ein 5xx-Code sein, da das Handy nicht erreicht werden kann Ein 3xx würde aber auch passen, da ein manuelles Redirect auf mein Festnetztelefon angegeben werden soll. Evtl wäre auch noch 204 zu verwenden. Oder gar ein 409, da der User zur falschen Zeit die Nummer gewählt hat. Oder 404, aber der impliziert ja dass ich 'für immer' weg bin. Ehrlich gesagt, ich bin etwas ratlos. Auf jeden Fall sollte es passend sein, 3xx ist Redirection, 4xx ist Client Error und 5xx Server Error. Oder etwa gar Fehler, wie ihn mein Squid-Proxy produziert?
Ich habe mal die entsprechenden Stellen zitiert:
HTTP:
204 No Content
The server has fulfilled the request but there is no new information to send back. If the client is a user agent, it should not change its document view from that which caused the request to be generated. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view. The response may include new metainformation in the form of entity headers, which should apply to the document currently in the user agent's active view.
The 204 response must not include an entity body, and thus is always ternminated by the first empty line after the header fields.
302 Moved Temporarily
The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client should continue to use the Request-URI for future requests. This response is only cachable if indicated by a Cache-Control or Expires header field.
If the new URI is a single location, its URL must be given by the Location field in the response. If more than one URI exists for the resource, the primary URL should be given in the Location field and the other URIs given in one or more URI-header fields. Unless it was a HEAD request, the Entity-Body of the response should contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent must not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
303 See Other
The response to the request can be found under a different URI and should be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new resource is not a replacement reference for the original Request-URI. The 303 response is not cachable, but the response to the second request may be cachable.
If the new URI is a single location, its URL must be given by the Location field in the response. If more than one URI exists for the resource, the primary URL should be given in the Location field and the other URIs given in one or more URI-header fields. Unless it was a HEAD request, the Entity-Body of the response should contain a short hypertext note with a hyperlink to the new URI(s).
404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (forbidden) can be used instead. The 410 (gone) status code should be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user may be able to resolve the conflict and resubmit the request. The response body should include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user-agent to fix the problem; however, that may not be possible and is not required.
Conflicts are most likely to occur in response to a PUT or PATCH request. If versioning is being used and the entity being PUT or PATCHed includes changes to a resource which conflict with those made by an earlier (third-party) request, the server may use the 409 response to indicate that it can't complete the request. In this case, the response entity should contain a list of the differences between the two versions in a format defined by the response Content-Type.
Squid, schon modifiziert:503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client should handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Was haltet ihr davon für am 'passensten'?The requested UPL (Uniform Person Locator) could not be approached.
While trying to retrieve the person "Moritz Augsburger"
The following error was encountered:
Unable to establish connection to Mobile Phone
Your request was saved in the answering machine log, including your telephone number if your telecommunication device was configured properly.
In Addition, you can leave a supplemental comment after the beep signal.
Und um das ganze authentisch auszigeben bin ich auch nach einem Programm, was mir englische Texte schön vorliest
