Object status

This is the list with all object status codes returned by Get Error Statistics, Translate Error String, or View Logs (GREP) tools as well as URL Health Check, Connectivity Problems, or Content Problems scenarios.

f log line

Object status

CodeDescription
aWhether SureRoute is enabled.
DSureRoute direct policy was used. The edge server chose to go directly to the origin server because it was fastest in the most recent race.
g‚ÄčAkamai‚Äč contacted an ICP peer server.
GForward request was made to satisfy an ICP peer.
iThe object was found in the file system buffer cache or the request was for an ESI fragment.
KThe request was for a prefetched object. The initial internal decision to prefetch can even be logged as a request line if the edgeservices:prefetch.fetch.log-r-lines tag is enabled.
kbypass-cach is turned on in metadata, or as the result of probabilistic ICP. It also indicates a POC2 fragment that was not cached because it was below the popularity threshold setting.
MThe request went forward to a metrocache backend. This flag will also be indicated on any sureroute mid-tier hops that might occur between metrocache frontends and backends.
NThe forward request was to a NetStorage domain.
OThis forward request was to an Intermediate Processing Agent (IPA).
oWhether the request was to the origin server.
p‚ÄčAkamai‚Äč contacted another hierarchy parent edge server.
PForward request was made to satisfy a cached child.
rWhether this is an authorization request to a remote authentication server.
tThe forward request was made under a POC StoreEntry.
xno-store was set in the metadata file.
YThe OCSP client certificate validation was used for this request (security.essl.slot-assignment.client-cert.ocsp.status).
yno-store was turned on in the response header.

Object status 2

CodeDescription
8The request is cacheable, regardless to icp.probabilistic and decisions to spread requests to all the machines in the region.
9PCHv2 impacted traffic (PCH for Site Shield) regardless of the feature rollout status.
aThe connection to the origin used IPv6.
BThe request forward because of the make-public-early unique-ID check.
bThe request was denied due to enabled feature causing the system to deny traffic based on forward request rate.
hThe request passed through the injected PCH tier.
iWhether the download map response from NSDS was internally converted to a 304 or not. If the object hash that ‚ÄčAkamai‚Äč receive from NSDS is the same as that of the refreshing entry, we will log an i in this field. If, the hash is different, nothing is logged.
JThe request has Site Shield policy on its path to origin even if the Site Shield hop was not reached.
MThe page rewriting was enabled for this request and at least one of the third-party content URL on the page were rewritten.
NThe page rewriting was enabled for this request but no third-party content URL was rewritten.
OA request to NSOS to fetch a fragment was made.
qThe QuickRetry feature stopped this request since it was insufficient.
RA download-resume request to NSOS was made.
rThe QuickRetry feature was applied to this request.
XAn edge server transformed content received from an origin or parent before, optionally, storing it in cache.

r log line

Object status

CodeDescription
aThis response was sent through the ESI processor.
DA default object was served.
eAn edge server served the last byte of the object to the client, whether the request is of byte-range type or not. If a range request was made, it means the edge server completed serving the a range request that included the last byte.
FThe request triggered prefetching of embedded objects based on the Prefetching feature.
fThe response was for an ESI fragment.
HA fail-action or fail-action2 was executed or and an edge server served the reply-arl for Request Queuing, in at least the fail-action2 serve-alternate - and probably serve-stale - case. This appears on the r line of the fail-action request, not the request that triggered the fail-action.
JThe request has Site Shield policy on its path to origin, even if the Site Shield hop was not reached.
kbypass_cache is turned on by metadata, or a result of probabilistic ICP, or when the downstream TTL is set by metadata and not by the response header.
Lbypass-cache is turned off in the response header.
l'bypass_cache' is turned on in the Cache-Control response header and honor-cc or honor-cc2 are on in the configuration or when downstream TTL was set by response header.
MThe request arrived as a metrocache request or went forward as a metrocache request. This flag will also be indicated on any SureRoute mid-tier hops that might occur between metrocache frontends and backends. Object status codes MP together are understood to indicate a request that arrived as a metrocache request. Object status codes Mp together are understood to indicate a request that went forward to a metrocache backend.
NThe request was processed over an anycast VIP and is marked as zero rated billing request.
nThe object was negatively cached, like a 404.
oThe origin server had been contacted.
qCached DCA output was served.
VThe object TTL was set in metadata.
WThe object TTL was set in response headers.
xWhen no-store is turned on by metadata and not disabled by !no-store in the response, or a result of probabilistic ICP, or when downstream TTL was set by metadata and not by the response header.
YThe OCSP client certificate validation was used for this request (security.essl.slot-assignment.client-cert.ocsp.status).
yno-store is turned on in the response header.
ZSome edge servers zipped the object at some point in our handling of the file.
zThe response was served to the client Content-Encoded: gzipped.

Object status 2

CodeDescription
8Response body inspection was on for this request (for example, for WAF rules).
CThe POST body was gzipped by an edge server and chunked.
cThe response was a constructed response based on edgeservices:construct-response metadata settings.
Hreporting:lds metadata was applied through Edge-Control response headers. This code identifies customers using Edge-Control features.
iRequest or response processing is skipped. See field r70 subfield waf= for the reason processing was skipped.
jThe request originated from a QUIC connection.
KThe WAF feature was enabled.
lThe object is too large based on security: large-file-protection thresholds.
OThe request was directed at an intermediate processing agent. The r line is only recorded if the log-r-line tag of the intermediate processing agent feature is on.
oTCP parameter settings were overridden through metadata.
QThe request was denied because of a WAF rule.
SThe Content policy stage was applied.
tThe response was served from a POC StoreEntry.
XThe intermediate processing agent feature was applied to this request.
YThe quota limit was reached when using an <assign:variable> function.

Object status 3

CodeDescription
4Indicates an internal request generated to fetch an OCSP staple.
aThe incoming request was served over IPv6.
bThe request used SPDY or HTTP/2.
DThe request resulted in a download receipt being generated.
dThe request or response was modified by the Content Adaptation Engine (edgeservices:content-adaptation).
fEnhanced Proxy Detection (EPD)- client IP of the request was matched in EPD database.
HA Client requested an OCSP certificate status during the SSL handshake but the edge server was unable to staple one because there was none available.
hAn edge server stapled an OCSP certificate status to the Client during the SSL handshake.
LStream being served is live. It can be forced by setting <reporting:is-content-live> to on.
MThe request used multidomain config to lookup the arlindex hostname.
oThe request used the global invalidation feature of EdgeKV.
pPartial POST body was used during request body inspection stage, for example for evaluation of WAF rules.
qPage rewrite module was enabled.
sSNI is enabled.