The server does not support the functionality required to fulfill the
request. This is the appropriate response when the server does not
recognize the request method and is not capable of supporting it for
any resource.
Or in this case the portfolio of Holger Friese. You can select between artworks, graphic design and hosted works. Or acess my CV, with a updated list of exhibitions and my bibliography.
Or you can step back into the design history of the homepage. From 1995 (made
as a student in Aachen), 1996 (hosted at The Thing Vienna), 1997-98 (hosted at
The Thing New York), 1999-2000 and 2001-2005 versions (hosted under this domainname).
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.
10.5.5 504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a
timely response from the upstream server it accessed in attempting to
complete the request.
Impressum - AGB (Stand 01.01.2001)
Fielding, et. al. Standards Track [Page 64]
RFC 2068 HTTP/1.1 January 1997
10.5.6 505 HTTP Version Not Supported
The server does not support, or refuses to support, the HTTP protocol
version that was used in the request message. The server is
indicating that it is unable or unwilling to complete the request
using the same major version as the client, as described in section
3.1, other than with this error message. The response SHOULD contain
an entity describing why that version is not supported and what other
protocols are supported by that server.
http://www.w3.org/Protocols/rfc2068/rfc2068