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

Code

Description

a

Whether SureRoute is enabled.

D

SureRoute 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.

G

Forward request was made to satisfy an ICP peer.

i

The object was found in the file system buffer cache or the request was for an ESI fragment.

K

The 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.

k

bypass-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.

M

The 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.

N

The forward request was to a NetStorage domain.

O

This forward request was to an Intermediate Processing Agent (IPA).

o

Whether the request was to the origin server.

p

​Akamai​ contacted another hierarchy parent edge server.

P

Forward request was made to satisfy a cached child.

r

Whether this is an authorization request to a remote authentication server.

t

The forward request was made under a POC StoreEntry.

x

no-store was set in the metadata file.

Y

The OCSP client certificate validation was used for this request (security.essl.slot-assignment.client-cert.ocsp.status).

y

no-store was turned on in the response header.

Object status 2

Code

Description

8

The request is cacheable, regardless to icp.probabilistic and decisions to spread requests to all the machines in the region.

9

PCHv2 impacted traffic (PCH for Site Shield) regardless of the feature rollout status.

a

The connection to the origin used IPv6.

B

The request forward because of the make-public-early unique-ID check.

b

The request was denied due to enabled feature causing the system to deny traffic based on forward request rate.

h

The request passed through the injected PCH tier.

i

Whether 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.

J

The request has Site Shield policy on its path to origin even if the Site Shield hop was not reached.

M

The page rewriting was enabled for this request and at least one of the third-party content URL on the page were rewritten.

N

The page rewriting was enabled for this request but no third-party content URL was rewritten.

O

A request to NSOS to fetch a fragment was made.

q

The QuickRetry feature stopped this request since it was insufficient.

R

A download-resume request to NSOS was made.

r

The QuickRetry feature was applied to this request.

X

An edge server transformed content received from an origin or parent before, optionally, storing it in cache.

r log line

Object status

Code

Description

a

This response was sent through the ESI processor.

D

A default object was served.

e

An 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.

F

The request triggered prefetching of embedded objects based on the Prefetching feature.

f

The response was for an ESI fragment.

H

A 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.

J

The request has Site Shield policy on its path to origin, even if the Site Shield hop was not reached.

k

bypass_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.

L

bypass-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.

M

The 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.

N

The request was processed over an anycast VIP and is marked as zero rated billing request.

n

The object was negatively cached, like a 404.

o

The origin server had been contacted.

q

Cached DCA output was served.

V

The object TTL was set in metadata.

W

The object TTL was set in response headers.

x

When 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.

Y

The OCSP client certificate validation was used for this request (security.essl.slot-assignment.client-cert.ocsp.status).

y

no-store is turned on in the response header.

Z

Some edge servers zipped the object at some point in our handling of the file.

z

The response was served to the client Content-Encoded: gzipped.

Object status 2

Code

Description

8

Response body inspection was on for this request (for example, for WAF rules).

C

The POST body was gzipped by an edge server and chunked.

c

The response was a constructed response based on edgeservices:construct-response metadata settings.

H

reporting:lds metadata was applied through Edge-Control response headers. This code identifies customers using Edge-Control features.

i

Request or response processing is skipped. See field r70 subfield waf= for the reason processing was skipped.

j

The request originated from a QUIC connection.

K

The WAF feature was enabled.

l

The object is too large based on security: large-file-protection thresholds.

O

The 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.

o

TCP parameter settings were overridden through metadata.

Q

The request was denied because of a WAF rule.

S

The Content policy stage was applied.

t

The response was served from a POC StoreEntry.

X

The intermediate processing agent feature was applied to this request.

Y

The quota limit was reached when using an <assign:variable> function.

Object status 3

Code

Description

4

Indicates an internal request generated to fetch an OCSP staple.

a

The incoming request was served over IPv6.

b

The request used SPDY or HTTP/2.

D

The request resulted in a download receipt being generated.

d

The request or response was modified by the Content Adaptation Engine (edgeservices:content-adaptation).

f

Enhanced Proxy Detection (EPD)- client IP of the request was matched in EPD database.

H

A Client requested an OCSP certificate status during the SSL handshake but the edge server was unable to staple one because there was none available.

h

An edge server stapled an OCSP certificate status to the Client during the SSL handshake.

L

Stream being served is live. It can be forced by setting <reporting:is-content-live> to on.

M

The request used multidomain config to lookup the arlindex hostname.

o

The request used the global invalidation feature of EdgeKV.

p

Partial POST body was used during request body inspection stage, for example for evaluation of WAF rules.

q

Page rewrite module was enabled.

s

SNI is enabled.


Did this page help you?