Results for: "Pathname"

Response class for Multi-Status (WebDAV) responses (status code 207).

The Multi-Status (WebDAV) response indicates that the server has received the request, and that the message body can contain a number of separate response codes.

References:

Response class for Already Reported (WebDAV) responses (status code 208).

The Already Reported (WebDAV) response indicates that the server has received the request, and that the members of a DAV binding have already been enumerated in a preceding part of the (multi-status) response, and are not being included again.

References:

Response class for See Other responses (status code 303).

The response to the request can be found under another URI using the GET method.

References:

Response class for Request Timeout responses (status code 408).

The server timed out waiting for the request.

References:

Response class for Request Timeout responses (status code 408).

The server timed out waiting for the request.

References:

Response class for Length Required responses (status code 411).

The request did not specify the length of its content, which is required by the requested resource.

References:

Response class for Payload Too Large responses (status code 413).

The request is larger than the server is willing or able to process.

References:

Response class for Range Not Satisfiable responses (status code 416).

The request entity has a media type which the server or resource does not support.

References:

Response class for Range Not Satisfiable responses (status code 416).

The request entity has a media type which the server or resource does not support.

References:

Response class for Expectation Failed responses (status code 417).

The server cannot meet the requirements of the Expect request-header field.

References:

Response class for Request Header Fields Too Large responses (status code 431).

An individual header field is too large, or all the header fields collectively, are too large.

References:

Response class for Unavailable For Legal Reasons responses (status code 451).

A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.

References:

Response class for Internal Server Error responses (status code 500).

An unexpected condition was encountered and no more specific message is suitable.

References:

Response class for Not Implemented responses (status code 501).

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

References:

Response class for Bad Gateway responses (status code 502).

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

References:

Response class for Service Unavailable responses (status code 503).

The server cannot handle the request (because it is overloaded or down for maintenance).

References:

Response class for Variant Also Negotiates responses (status code 506).

Transparent content negotiation for the request results in a circular reference.

References:

No documentation available
No documentation available

OpenTimeout, a subclass of Timeout::Error, is raised if a connection cannot be created within the open_timeout.

ReadTimeout, a subclass of Timeout::Error, is raised if a chunk of the response cannot be read within the read_timeout.

WriteTimeout, a subclass of Timeout::Error, is raised if a chunk of the response cannot be written within the write_timeout. Not raised on Windows.

Base class of exceptions from OptionParser.

Raises when ambiguously completable string is encountered.

Raises when there is an argument for a switch which takes no argument.

Search took: 3ms  ·  Total Results: 3265