Response class for Gateway Timeout responses (status code 504).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
References:
Response class for Gateway Timeout responses (status code 504).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
References:
Response class for Variant Also Negotiates responses (status code 506).
Transparent content negotiation for the request results in a circular reference.
References:
Response class for Network Authentication Required responses (status code 511).
The client needs to authenticate to gain network access.
References:
Map from option/keyword string to object with completion.
A cache that can be used to quickly compute code unit offsets from byte offsets. It purposefully provides only a single [] method to access the cache in order to minimize surface area.
Note that there are some known issues here that may or may not be addressed in the future:
The first is that there are issues when the cache computes values that are not on character boundaries. This can result in subsequent computations being off by one or more code units.
The second is that this cache is currently unbounded. In theory we could introduce some kind of LRU cache to limit the number of entries, but this has not yet been implemented.
This represents a location in the source.