Error codes

This is the list of error codes returned by Get Error Statistics or Translate Error String tools together with short descriptions.

Error codeError nameReason
0.x.x.xERR_ACCESS_DENIED|rqacCustomThe request was denied by a Web Application Firewall or Bot Manager rule configured. The rule is set to use a custom deny page.
1.x.x.xERR_READ_TIMEOUTThe forward connection to the origin server from the edge server timed out.
2.x.x.xERR_LIFETIME_EXPThe request's lifetime was exceeded.
3.x.x.xERR_READ_ERRORThe TCP connection from the edge server to the origin server was broken before the headers and object were successfully downloaded. If this happens even though the origin is healthy, you can try lowering the persistent connection timeout to be lower than origin’s setting, or you can try disabling the persistent connection feature on the edge server.
4.x.x.xERR_WRITE_ERRORUnable to close the socket to the client.
5.x.x.xERR_SHUTTING_DOWNThe edge server received the shutdown order and is shutting down.
6.x.x.xERR_CONNECT_FAILConnection to the origin server from the edge server timed out. The connection was never established.
7.x.x.xERR_INVALID_REQThe request's URL is not RFC compliant (the error includes malformed) or there could be invalid HTTP headers in the request that cause it to be rejected. If this request uses DRM, check the token.
8.x.x.xERR_UNSUP_REQUnsupported request.
9.x.x.xERR_INVALID_URLInternal error. For more details, contact the support team.
10.x.x.xERR_SOCKET_FAILUREInternal error. For more details, contact the support team.
11.x.x.xERR_DNS_FAILThe origin server IP address couldn't be resolved from the origin hostname.
12.x.x.xERR_CANNOT_FORWARDInternal error. For more details, contact the support team.
13.x.x.xERR_FORWARDING_DENIEDThe request was not sent to the origin server. This is normal in the case of SureRoute test objects, when some requests are interrupted by the edge server if the fastest path to the origin has already been determined.
14.x.x.xERR_NO_RELAYInternal error. For more details, contact the support team.
15.x.x.xERR_ZERO_SIZE_OBJECTA response from the origin server has zero length.
16.x.x.xERR_URN_RESOLVEInternal error. For more details, contact the support team.
17.x.x.xERR_BAD_DEBUG_COOKIEInternal error. For more details, contact the support team.
18.x.x.xERR_ACCESS_DENIEDThe client server was not authorized to access requested object or the origin server.
18.1x.x.xERR_ACCESS_DENIED|*A string after the bar character that is not listed here likely means that the denial was based on auth:acl.deny metadata. The string is the first position in the deny list that caused the denial.
18.2x.x.xERR_ACCESS_DENIED | bad_cn_matchThe CN on the certificate didn't match the host header.
18.3x.x.xERR_ACCESS_DENIED|bad_update_urlThe request from mupdater contained invalid characters.
18.4x.x.xERR_ACCESS_DENIED|connect_loopThe CONNECT method detected a loop.
18.5x.x.xERR_ACCESS_DENIED|es_loadingThe edge server received an updated edgescape database that is still loading.
18.6x.x.xERR_ACCESS_DENIED|ff_v1arl_nomdtThe unsupported version 1 of the ARL detected.
18.7x.x.xERR_ACCESS_DENIED|fp_auth_failedFingerprint authentication failed.
18.8x.x.xERR_ACCESS_DENIED|fwd_aclConnection to forward host is not allowed because the host is not added in the Allowed Origins.
18.9x.x.xERR_ACCESS_DENIED|fwd_acl_sslConnection to forward host is not allowed because the host is not added in the Allowed Origins.
18.10x.x.xERR_ACCESS_DENIED|ipa_amplificationA client request was received with the internal edge server header.
18.11x.x.xERR_ACCESS_DENIED|ipv6-clientInternal error. For more details, contact the support team.
18.12x.x.xERR_ACCESS_DENIED|legacy_aclConnection to forward host is not allowed because the host is not added in the Allowed Origins.
18.13.x.x.xERR_ACCESS_DENIED|loop_*Loop detected.
18.14x.x.xERR_ACCESS_DENIED|mdtAccess is denied for this transaction per the metadata configuration.
18.15x.x.xERR_ACCESS_DENIED|mdt_update_failedMupdater request failed.
18.16x.x.xERR_ACCESS_DENIED|post_not_allowedPOST requests are blocked in the metadata configuration.
18.17x.x.xERR_ACCESS_DENIED|prefetch_pushThe edge server received a PREFETCH_PUSH request from a peer, but this type of request was blocked in the metadata configuration.
18.18x.x.xERR_ACCESS_DENIED|ptk_default-deny-reasonThe request was blocked by the Client IP. Check Allowed and Blocked lists in the configuration.
18.19x.x.xERR_ACCESS_DENIED|purge_*Purge failed.
18.20x.x.xERR_ACCESS_DENIED|purge_ipcache_*IP cache purge failed.
18.21x.x.xERR_ACCESS_DENIED|reqmod_*Request-mod failed.
18.22x.x.xERR_ACCESS_DENIED|reqsatRequest-sat failed.
18.23x.x.xERR_ACCESS_DENIED|respmodResponse-mod failed.
18.24x.x.xERR_ACCESS_DENIED|ssl_port_aclServer refused to go forward to a non-standard origin port.
18.25x.x.xERR_ACCESS_DENIED|store_rebuildingMupdater request was denied because the store is rebuilding.
18.26x.x.xERR_ACCESS_DENIED|streamauth*Streamauth was not allowed or failed.
18.27x.x.xERR_ACCESS_DENIED|vrThe request was denied due to limits placed in the configuration for blocking requests when the overall traffic goes higher than the configured threshold.
18.28x.x.xERR_ACCESS_DENIED|wafThe request was denied by the configured Web Application Firewall rules.
18.29x.x.xERR_ACCESS_DENIED|Sec_Serve_AlternateThe request was denied by the configured Bot Manager rules.
18.32x.x.xERR_ACCESS_DENIED|china_cdnRequest was denied because it was going to a ChinaCDN machine from outside China.
18.33x.x.x, 18.dx.x.xERR_ACCESS_DENIED|BotMan_InternalRequest was considered as Bot Manager Internal Request and denied potentially due to security config misconfiguration.
19.x.x.xERR_CACHE_ACCESS_DENIEDInternal error. For more details, contact the support team.
20.x.x.xERR_CACHE_MGR_ACCESS_DENIEDInternal error. For more details, contact the support team.
27.x.x.xERR_CLIENT_ABORTThe request was not sent to the origin server. This is normal in the case of SureRoute test objects, when some requests are interrupted by the edge server if the fastest path to the origin has already been determined.
29.x.x.xERR_FWD_SSL_OUT_OF_HANDSHAKESInternal error. For more details, contact the support team.
30.x.x.xERR_FWD_SSL_HANDSHAKEInternal error. For more details, contact the support team.
31.x.x.xERR_FWD_SSL_BAD_CERTInternal error. For more details, contact the support team.
32.x.x.xERR_NO_ORIGIN_CLIENT_AUTHThe server didn't request a certificate which is opposite to what was set in the metadata.
33.x.x.xERR_DCA_MAX_POST_SIZEInternal error. For more details, contact the support team.
34.x.x.xERR_DCA_BAD_WAR_REQInternal error. For more details, contact the support team.
35.x.x.xERR_DCA_MAX_WAR_SIZEInternal error. For more details, contact the support team.
36.x.x.xERR_DCA_MAX_ESI_INCLUDE_SIZEInternal error. For more details, contact the support team.
37.x.x.xERR_DCA_CONTAINERInternal error. For more details, contact the support team.
38.x.x.xERR_FWD_PCONN_SEC_UPGRADEThe PConn is HTTPS but the client expects HTTP. Check if the metadata is not misconfigured. For example, the port doesn't match the protocol being used.
39.x.x.xERR_FWD_PCONN_SEC_DOWNGRADEThe PConn is HTTP but the client expects HTTPS. Check if the metadata is not misconfigured. For example, the port doesn't match the protocol being used.
40.x.x.xERR_GHOSTMON_CHK_MSGThis request was a liveness check request generated by an edge server.
41.x.x.xERR_CLIENT_ABORT_SLOW_DNSInternal error. For more details, contact the support team.
42.x.x.xERR_FWD_SSL_BAD_MDT_CIPHERSThe ssl:security.ssl.forward-ciphers is not configured correctly.
43.x.x.xERR_FWD_SAME_REGIONThe edge server attempted to contact its own region as the cache-h parent. After this error, it will attempt the next forward server, usually the origin.
44.x.x.xERR_DANGEROUS_PORTThe edge server couldn't go forward to requested port because it's in the deny-port list.
45.x.x.xERR_FWD_RATE_LIMIT_Q_TIMEOUTThis request exceeded its allowed wait time in the queue set by fwd-rate-limit-queue-max-wait-ms.
46.x.x.xERR_FWD_RATE_LIMIT_Q_FILLED_UPThe forward request was evicted from the forward queue. The queue had reached its limit and a request with higher priority or earlier request-header parse time took its spot.
47.x.x.xERR_FWD_RATE_LIMIT_Q_FULLThe forward request couldn't be added to the forward queue because it was full.
48.x.x.xERR_FWD_RATE_LIMIT_HOST_HASH_FULLThe forward request couldn't be handled because the host hash was full and other hosts were handling their requests.
49.x.x.xERR_FWD_RATE_LIMIT_NO_FREE_IPSForward Rate Limiting failed for this request with an unspecified reason. This error excludes the following cases:
- This request exceeded its allowed wait time in the queue set by fwd-rate-limit-queue-max-wait-ms.
- The request was evicted from the forward queue because the queue had reached its limit and a request with higher priority or earlier request-header parse time took its spot.
- The request couldn't be added to the forward queue because it was full.
- The request couldn't be handled because the host hash was full and other hosts were handling their requests.
50.x.x.xERR_URL_DIS_AUTHURL-based edge authorization feature rejected this request.
51.x.x.xERR_NO_CLIENT_CERTInternal error. For more details, contact the support team.
52.x.x.xERR_INVALID_CLIENT_CERTInternal error. For more details, contact the support team.
54.x.x.xERR_FWD_CERT_MISSINGThe certificate has not yet been loaded. Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID.
55.x.x.xERR_FWD_CERT_INACTIVEThe certificate's auth.ssl-fwd-certs.status flag was off. Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID.
56.x.x.xERR_FWD_CERT_INVALIDStrict certificate checking was on and the certificate was invalid.Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID.
57.x.x.xERR_OCSP_NOT_HTTP_OKThe HTTP response code was not 200 OK.
58.x.x.xERR_OCSP_BAD_RESPParsing of the DER encoded response failed.
59.x.x.xERR_OCSP_BAD_BASICRESPThe basicResponse within the OCSP response was either not id-pkix-ocsp-basic or it couldn't be parsed.
60.x.x.xERR_OCSP_STAT_MALFORMEDREQUESTThe responder responded with a malformedRequest message indicating that edge server's message didn't conform to the OCSP syntax.
61.x.x.xERR_OCSP_STAT_INTERNALERRORThe responder responded with an internalError message indicating that it encountered an internal error.
62.x.x.xERR_OCSP_STAT_TRYLATERThe responder responded with the tryLater message indicating that the edge server should retry later. Edge serves retry against a secondary responder (if any) or when the user makes another request.
63.x.x.xERR_OCSP_STAT_SIGREQUIREDThe responder responded with a sigRequired message indicating that the edge server should sign the request. Edge servers don't support signing of the request at this point.
64.x.x.xERR_OCSP_STAT_UNAUTHORIZEDThe responder responded with the unauthorized message indicating that the edge server is not authorized to make a query against the given responder.
65.x.x.xERR_OCSP_STAT_UNKNOWNThe responder responded with a message that the edge server didn't understand.
66.x.x.xERR_OCSP_NO_NONCEThe edge server sent a nonce to the responder but the responder didn't send a nonce.
67.x.x.xERR_OCSP_BAD_NONCEThe edge server sent a nonce to the responder but the responder sent a different nonce.
68.x.x.xERR_OCSP_VERIFYThe verification of the basicResponse failed. Check cache.log for failure details.
69.x.x.xERR_OCSP_CERTID_NOT_IN_RESP1One of the certificate IDs that was in edge server's request was not in the OCSP response.
70.x.x.xERR_OCSP_CERTID_NOT_IN_RESP2One of the certificate IDs that was in edge server's request was not in the OCSP response.
71.x.x.xERR_OCSP_CERT_REVOKED_NOSTATUSThe certificate was revoked and the responder didn't specify why.
72.x.x.xERR_OCSP_CERT_REVOKED_UNSPECIFIEDThe certificate was revoked and the responder specifically stated the reason to be unspecified.
73.x.x.xERR_OCSP_CERT_REVOKED_KEYCOMPROMISEThe certificate was revoked and the responder returned the keyCompromise reason code.
74.x.x.xERR_OCSP_CERT_REVOKED_CACOMPROMISEThe certificate was revoked and the responder returned the caCompromise reason code.
75.x.x.xERR_OCSP_CERT_REVOKED_AFFILIATIONCHANGEDThe certificate was revoked and the responder returned the affilicationChanged reason code.
76.x.x.xERR_OCSP_CERT_REVOKED_SUPERSEDEDThe certificate was revoked and the responder returned the superseded reason code.
77.x.x.xERR_OCSP_CERT_REVOKED_CESSATIONOFOPERATIONThe certificate was revoked and the responder returned the cessationOfOperation reason code.
78.x.x.xERR_OCSP_CERT_REVOKED_CERTIFICATEHOLDThe certificate was revoked and the responder returned the certifciateHold reason code.
79.x.x.xERR_OCSP_CERT_REVOKED_REMOVEFROMCRLThe certificate was revoked and the responder returned the removeFromCrl reason code.
80.x.x.xERR_OCSP_CERT_REVOKED_STATUS_UNRECOGNThe certificate was revoked and the edge server didn't recognize the returned reason code.
81.x.x.xERR_OCSP_CERT_UNKNOWNThe OCSP responder didn't recognize the user's certificate. The edge server considers the certificate invalid.
82.x.x.xERR_OCSP_CERT_STATUS_UNRECOGNThe edge server didn't recognize the certificate status given by the responder. The edge server considers the certificate invalid.
83.x.x.xERR_OCSP_THIS_UPD_MISSINGThe this-update field was missing from the response.
84.x.x.xERR_OCSP_THIS_UPD_INVALIDThe this-update field couldn't be parsed.
85.x.x.xERR_OCSP_THIS_UPD_TOO_OLDThe this-update field was too old based on the security.essl.slot-assignment.client-cert. ocsp.responder.this-upd-allowed-past-diff setting.
86.x.x.xERR_OCSP_THIS_UPD_TOO_AHEADThe this-update field was way passed the current time based on the security.essl.slot-assignment.client-cert. ocsp.responder.this-upd-allowed-future-diff setting.
87.x.x.xERR_OCSP_NEXT_UPD_INVALIDThe next-update field couldn't be parsed.
88.x.x.xERR_OCSP_NEXT_UPD_TOO_OLDThe next-update field was too old based on the security.essl.slot-assignment.client-cert. ocsp.responder.next-upd-allowed-future-diff setting.
89.x.x.xERR_OCSP_NEXT_UPD_TOO_AHEADThe next-update field was way passed the current time based on the security.essl.slot-assignment.client-cert. ocsp.responder.next-upd-allowed-future-diff setting.
90.x.x.xERR_OCSP_THIS_UPD_AHEAD_OF_NEXTThe this-update field was ahead of the next-update field.
91.x.x.xERR_OCSP_INTERNALAn internal error occurred in the edge server while validating the response. Check cache.log for details.
92.x.x.xERR_OCSP_NOT_DONEOCSP processing failed. Check cache.log for details.
93.x.x.xERR_PREFETCH_LIMITOne of the limits on the number of forward requests based on the Prefetching feature was exceeded. The error can apply to edge servers or to the customer.
94.x.x.xERR_FWD_ENTRY_ABORTEDThe forward connection to the origin from the edge server was interrupted.
95.x.x.xERR_CLIENT_READ_TIMEOUTThe edge server timed out waiting for data from the client. This is more likely to be seen on POST requests.
96.x.x.xERR_FWD_HASHED_SERIAL_NO_BACKEND_IPY-map constructed with hashed serial didn't yield a backend IP in the response when resolved. The response is usually a VIP. The edge server forwards the request normally either to a cache parent or the origin.
97.x.x.xERR_CONNECT_TIMEOUTConnection to the origin server from the edge server timed out. The connection was never established.
98.x.x.xERR_SSL_CONNECT_TIMEOUTThe SSL connection to the origin server from the edge server timed out.
99.x.x.xERR_DNS_TIMEOUTDNS lookup timeout.
100.x.x.xERR_SUREROUTE_DNS_FAILAkaroute RProxy Marker error. The DNS resolution for a parent came back as 0.0.0.1 or 0.0.0.2.
101.x.x.xERR_DNS_IN_REGIONThis is not an error and doesn’t indicate any failure in transaction. This means that an edge server contacted a different server in the same location. When this condition occurs, the edge server simply goes to the origin server to retrieve the content.
102.x.x.xERR_NO_GOOD_FWD_IPThis is triggered by the Origin Health Detect feature. This code means that edge server intentionally didn't go forward to the origin because the origin is flagged as bad due to too many failures in retrieving content from it. This feature reduces the load on origin and gives some time for the origin to recover. As the origin starts to recover and get healthy, these errors go away.
103.x.x.xERR_HTTP_CONNECT_FAILThe HTTP connect failed.
106.x.x.xERR_RSYNC_OBSOLETEInternal error. For more details, contact the support team.
107.x.x.xERR_WAR_ABORTThe WAR file was interrupted.
108.x.x.xERR_ESI_BUF_ABORTASI buffer copy operation was interrupted, most likely due to the client action.
109.x.x.xERR_ESI_RESPInternal error. For more details, contact the support team.
110.x.x.xERR_STORE_COPYInternal error. For more details, contact the support team.
111.x.x.xERR_FP_MISMATCHRead error happened due to fingerprint mismatch.
112.x.x.xERR_GZIPRead error happened due to compression.
113.x.x.xERR_PARTIAL_FWD_REJECTRead error happened due to partial forward reject.
114.x.x.xERR_QUEUE_MKDIRWrite error happened due to the Mkdir in the client queue code failure.
115.x.x.xERR_QUEUE_FOPENInternal error. For more details, contact the support team.
116.x.x.xERR_QUEUE_WRITEWrite error happened due to the write file in the client queue code failure.
117.x.x.xERR_QUEUE_POST_TOO_BIGWrite error happened due to too big POST body for the client queue.
118.x.x.xERR_QUEUE_ENQWrite error happened due to the enqueuing the current request failure.
119.x.x.xERR_NO_FWD_HOSTSThe edge server was unable to resolve any of the potential forward hostnames (origin or cache hierarchy parent or SureRoute parent) to an IP address. This indicates either a DNS problem or a problem with the map names being misconfigured or nonexistent.
121.x.x.xERR_OBJ_OUT_OF_DATEThe response object from origin is out of date.
122.x.x.xERR_BAD_CHUNKED_ENCThe origin received bad chunked encoding.
123.x.x.xERR_WIN32_READ_ERRThe forward connection to the origin server broke.
124.x.x.xERR_GM_SUPPRESSED_ERRInternal error. For more details, contact the support team.
125.x.x.xERR_SSL_POST_RENEGSSL client-side session renegotiation was requested under a POST request with the feature being turned off.
126.x.x.xERR_FWD_CONTENT_MD5Internal error. For more details, contact the support team.
127.x.x.xERR_CLIENT_CONTENT_MD5Internal error. For more details, contact the support team.
128.x.x.xERR_PURGE_SEQ_OUT_OF_DATEThe forward connection to the origin was interrupted due to a purge sequence number mismatch.
129.x.x.xERR_POC_MS_FRAG_SIZE_CHANGEDThe client connection was interrupted because all of the following cases occurred:
- The master entry the client was attached to became private, the object got purged or revalidated and the TTL expired.
- More fragments on behalf of the users attached to the private master had to be downloaded.
- The newly created public master had a different fragment size.
130.x.x.xERR_POC_MS_POC_OFFThe client connection was interrupted because all of the following cases occurred:
- The master entry the client was attached to became private, the object got purged or revalidated and the TTL expired.
- More fragments on behalf of the users attached to the private master had to be downloaded.
- The newly created public StoreEntry was not a POC entry.
131.x.x.xERR_POC_MS_NO_PUBLIC_ENTRYInternal error. For more details, contact the support team.
132.x.x.xERR_POC_FWD_NOT_206The HTTP response code was not 206 Partial Content.
133.x.x.xERR_POC_FWD_NO_CONTLENThe response had no content-length header.
134.x.x.xERR_POC_FWD_DCA_OUTPUTX-Akamai-DCA-Output-Maxage was present in the response.
135.x.x.xERR_POC_FWD_GZIPPEDThe response was compressed.
136.x.x.xERR_POC_FWD_NO_RANGEThe response had no content-range header.
137.x.x.xERR_POC_FWD_NO_ELENThe entity-length field was not a specific number in the content-range response header.
138.x.x.xERR_POC_FWD_NO_OFFSETThe content-range header had no beginning offset.
139.x.x.xERR_POC_FWD_BAD_RLENUnexpected length of the range in the content-range response header.
140.x.x.xERR_POC_FWD_LEN_MISMATCHThe content-length header didn't match the number of bytes given with the content-range header.
141.x.x.xERR_POC_FWD_OFFSET_MISMATCHThe beginning offset of the content-range response header didn't match the beginning offset of the range request header.
142.x.x.xERR_POC_FWD_MS_NONCHThe response to the initial POC range request indicates the object is not cacheable. Either this object is misconfigured on the origin or POC shouldn't be applied to it.
143.x.x.xERR_POC_FWD_OBJ_TOO_SMALLThe response object is smaller than what is permitted by the configuration settings.
144.x.x.xERR_POC_FWD_OBJ_TOO_BIGThe response object is larger than what is permitted by the configuration settings.
145.x.x.xERR_POC_FWD_ETAG_NONEcache.poc2.trust-etag is on and there was no ETag in the response.
146.x.x.xERR_POC_FWD_ETAG_WEAKcache.poc2.trust-etag is on and the ETag in the response was tagged as weak.
147.x.x.xERR_POC_FWD_ETAG_BADcache.poc2.trust-etag is on and the ETag in the response had a non-HTTP compliant format. The value has to be surrounded by double quotes with an optional "W/" indicating weak ETag.
148.x.x.xERR_POC_FWD_LASTMOD_NONEcache:poc2.trust-lastmod is on and there was no Last-Modified header in the response.
149.x.x.xERR_POC_FWD_LASTMOD_BADcache:poc2.trust-lastmod is on and the Last-Modified header in the response had an incorrect format. On the f line, they're always printed time when the inconsistent fragment was encountered and on the r line whether the connection was interrupted. Otherwise, the r line have a status code indicating that possibly an inconsistent object was served.
150.x.x.xERR_POC_FWD_OBJ_SIZE_CHANGEDThe object consistency verification failed because the object size is different on the current master and a fragment.
151.x.x.xERR_POC_FWD_ETAG_CHANGEDThe object consistency verification failed because the ETag is different on the current master and a fragment. This may mean that one of the ETags was either different or badly formatted or the ETag was missing from one of them.
152.x.x.xERR_POC_FWD_LASTMOD_CHANGEDThe object consistency verification failed because the last-modified time is different between on the current master and a fragment. This may mean that one of the last-modified times was different or badly formatted or the last-modified time was missing from one of them.
153.x.x.xERR_POC_FWD_AK_GZIPPEDThe response had the X-Ak-Gzip-Downstream header indicating that a peer or parent edge server compressed the response.
154.x.x.xERR_POC_FWD_TR_ENCThe response was transfer-encoded. The edge server retries with a regular forward request.
155.x.x.xERR_POC_FWD_G2G_ABORTThe connection had to be interrupted because the in-coming client is another edge server and the origin drops the connection after the response was being received.
156.x.x.xERR_POC_FWD_CANT_CREATE_MSFailed to establish a master entry due to some error on the forward side. The master is converted to a regular entry with a 503 HTTP status code.
157.x.x.xERR_POC_FWD_FRAG_ABORTFailed to fetch a fragment most likely due to forward server breaking off. Check the f line for details. The fragment's status code is set to 503 in this case. This could also occur when an incorrect client range makes it to the forward side of the edge server.
158.x.x.xERR_POC_TC_FPThe request was for a TC 2/3 object and POC2 was on and they are not compatible.
159.x.x.xERR_POC_FWD_ABORTFailed to fetch a fragment most likely due to forward server breaking off. Check the f line for details. The fragment's status code is set to 503 in this case. This could also occur when an incorrect client range makes it to the forward side of the connecting client. If cache:poc2.hide-forward-errs-from-user is on, this error won't show in the logs.
160.x.x.xERR_RAW_ABORTInternal error. For more details, contact the support team.
161.x.x.xERR_DCA_BAD_ECFILE_REQInternal error. For more details, contact the support team.
162.x.x.xERR_OCSPInternal error. For more details, contact the support team.
163.x.x.xERR_POCInternal error. For more details, contact the support team.
164.x.x.xERR_DRM_ACCESS_DENIEDInternal error. For more details, contact the support team.
166.x.x.xERR_HRS_SPACE_IN_HDR_NAMEPossible request smuggling detected. There was a space in the name of a request header.
167.x.x.xERR_HRS_EMPTY_CONTINUATIONPossible request smuggling detected. The header ended in CR/LF and the following line contained only spaces.
168.x.x.xERR_HRS_BARE_CRS_IN_HDRPossible request smuggling detected. There was a bare carriage returned and space within the headers.
169.x.x.xERR_HRS_DUP_CONTENT_LENPossible request smuggling detected. There was a second content-length header in the request.
171.x.x.xERR_WM_ACCESS_DENIEDWatermark Authentication failed.
172.x.x.xERR_OBJ_TOO_BIGThe response object is larger than what is permitted by the configuration settings.
173.x.x.xERR_SSL_POST_RENEG_TOO_BIGSSL client-side session renegotiation was requested under a POST request but the POST body size was greater than permitted by the configured settings.
174.x.x.xERR_METADATA_APPLY_FAILUREInternal error. For more details, contact the support team.
175.x.x.xERR_FWD_RESIGNED_CERTA copy or signing operation failed when trying to resign the client certificate for transfer to the origin.
176.x.x.xERR_SSL_RENEGInternal error. For more details, contact the support team.
177.x.x.xERR_FLV_SEEKInternal error. For more details, contact the support team.
178.x.x.xERR_CHUNK_INCOMPLETEThe origin didn't send the last chunk of a file using Transfer-Encoding and the connection timed out. The edge server assumes that it has received the complete file, but treats it as uncacheable and logs the error. This behavior is controlled by the metadata.
179.x.x.xERR_NO_STICKY_PCONNInternal error. For more details, contact the support team.
180.x.x.xERR_ICP_DEADLOCK_DETECTThe request was from another in-region edge server and the current edge server has a pending forward request to that edge server for the same object. This request is rejected since it may result in a deadlock.
181.x.x.xSTREAMING_BAD_REQUESTInternal error. For more details, contact the support team.
182.x.x.xSTREAMING_UNAUTHORIZEDInternal error. For more details, contact the support team.
183.x.x.xSTREAMING_NOT_FOUNDInternal error. For more details, contact the support team.
184.x.x.xICP_PUBLIC_EARLY_RESPONSEInternal error. For more details, contact the support team.
185.x.x.xSTORE_ENTRY_LOOP_DETECTInternal error. For more details, contact the support team.
186.x.x.xERR_FWD_BAD_HEADERSInvalidForwardReply: The response headers from the origin or the edge server parent were malformed or too large. The error occurs when the HTTP response status line is missing or malformed or when the origin or parent response headers exceed the size limit. This can often occur if Pragma: akamai-x-get-extracted-values was specified in the request to perform debugging, and there are a large number of X-Session-Info response headers.
187.x.x.xERR_MP4_SEEKInternal error. For more details, contact the support team.
188.x.x.xERR_STREAMING_VERIFICATION_FAILEDInternal error. For more details, contact the support team.
189.x.x.xERR_SSL_INSECURE_RENEGOTIATIONConnection interrupted with HTTP_FORBIDDEN because of not secure ESSL client-side renegotiation.
190.x.x.xERR_SSL_TLS_SECURITY_EXTConnection interrupted with HTTP_FORBIDDEN because of security:enforce-tls-security-extension.* on and the TLS secure renegotiation extension not in effect.
191.x.x.xERR_POC_FWD_CONTENT_MD5_CHANGEDInternal error. For more details, contact the support team.
192.x.x.xERR_POC_FWD_CONTENT_MD5_NONEInternal error. For more details, contact the support team.
193.x.x.xERR_IPTV_BAD_REQUESTInternal error. For more details, contact the support team.
194.x.x.xERR_IPTV_NOT_FOUNDInternal error. For more details, contact the support team.
195.x.x.xERR_ADOBE_ERRORInternal error. For more details, contact the support team.
196.x.x.xERR_UITS_BAD_REQUESTInternal error. For more details, contact the support team.
197.x.x.xERR_ORIGIN_HOST_LOOPThe origin hostname that the edge server was about to go forward to matches the name in the client request Host header indicating a loop in the forward logic. This behavior is controlled by the metadata tag network:dns.rollback-origin-host-loop-check.
198.x.x.xERR_IPV6_SERVICE_UNAVAILABLEInternal error. For more details, contact the support team.
199.x.x.xERR_AUTH_BROWSER_TOKEN_FAILEDInternal error. For more details, contact the support team.
200.x.x.xERR_TRANSFORMINGConnection interrupted. The edge server encountered an error in the midst of transforming content after it had already sent at least one byte of data to the client. The message after the '|' refines the nature of the error.
201.x.x.xERR_SILVERLIGHTInternal error. For more details, contact the support team.
202.x.x.xERR_ENCRYPTInternal error. For more details, contact the support team.
203.x.x.xERR_FWD_CAE_HEADERSThis error indicates that the response headers from CAE failed the verification and forward request were treated as failed.
204.x.x.xERR_TPCAInternal error. For more details, contact the support team.
205.x.x.xERR_TRANSFORMATION_POOLEdge server encountered an error related to the thread pool that performs content transformations. There should be currently no way for this error to actually occur. Problems with transformed content trigger ERR_TRANSFORMING instead, the most important types of which are documented above.
208.x.x.xERR_STREAMING_BAD_CONNECTIONInternal error. For more details, contact the support team.
209.x.x.xERR_SWAPMETA_FAILInternal error. For more details, contact the support team.
210.x.x.xERR_BAD_SWAPFILE_APPENDInternal error. For more details, contact the support team.
211.x.x.xERR_SWAPMETA_PARSE_FAILInternal error. For more details, contact the support team.
212.x.x.xERR_GETZIP_PROTOCOL_ERRORInternal error. For more details, contact the support team.
213.x.x.xERR_P2G_AUTHPartner Authentication failures. The possible refined error messages for this error currently are:
- scc_partnerauth_failed, when an SCC log line POST is rejected because partner authentication failed.
- scc_partnerauth_notenabled, when an SCC log line POST is rejected because partner authentication is not enabled.
214.x.x.xERR_FWD_STORAGE_BAD_RESPONSEInternal error. For more details, contact the support team.
215.x.x.xERR_HT_FAILInternal error. For more details, contact the support team.
216.x.x.xERR_STREAMING_MULTIInternal error. For more details, contact the support team.
217.x.x.xERR_OUT_OF_RESOURCESInternal error. For more details, contact the support team.
218.x.x.xERR_CONTENT_POLICYInternal error. For more details, contact the support team.
219.x.x.xERR_EPD_ACCESS_DENIEDThe request was denied due to the Enhanced Proxy Detection feature. The error should include a description explaining the reason of the denial.
220.x.x.xERR_PLAYLIST_MODIFICATIONInternal error. For more details, contact the support team.
221.x.x.xERR_FIRST_BYTE_TIMEOUTConnection to the forward server timed out.
222.x.x.xERR_DELEGATORInternal error. For more details, contact the support team.
224.x.x.xERR_SSL_HTTP2_NO_RENEGOTIATIONInternal error. For more details, contact the support team.
225.x.x.xERR_RESOURCE_INTEGRITY_FAILEDInternal error. For more details, contact the support team.
226.x.x.xERR_HTTP2_ERRORInternal error. For more details, contact the support team.
227.x.x.xERR_INVALID_REQ_NOORIGINMDTInternal error. For more details, contact the support team.
228.x.x.xERR_WEBSOCKET_READ_TIMEOUTInternal error. For more details, contact the support team.
229.x.x.xERR_WEBSOCKET_PRUNEInternal error. For more details, contact the support team.
230.x.x.xERR_COMBINED_STOREInternal error. For more details, contact the support team.
231.x.x.xERR_HRS_HOST_HEADER_MISMATCHPossible request smuggling detected. There were multiple mismatching host headers or a mismatch between the host in the URI and a host header in the request.
232.x.x.xERR_BROTLIInternal error. For more details, contact the support team.
233.x.x.xERR_ERR_NETPInternal error. For more details, contact the support team.
234.x.x.xERR_MANIFEST_MANIPULATIONInternal error. For more details, contact the support team.
236.x.x.xERR_FRP_DENIEDThe forward robustness protection feature is active and it denies a forward request.
237.x.x.xERR_MID_HEADER_ABORTInternal error. For more details, contact the support team.
238.x.x.xERR_OCSP_CERTID_BAD_ALGO_IN_RESPInternal error. For more details, contact the support team.
239.x.x.xERR_POC_MS_OBJ_SIZE_CHANGEDInternal error. For more details, contact the support team.
240.x.x.xERR_STORE_HTTP_STATUS_NONEThe response had no status code.
241.x.x.xERR_OUTPUT_FILTER_EXCEED_MAX_BUF_SIZEInternal error. For more details, contact the support team.
242.x.x.xERR_GRID_INTEGRITY_CREATE_OBJECTInternal error. For more details, contact the support team.
243.x.x.xERR_POC_INTEG_NO_PUBLIC_ORIG_ENTRYInternal error. For more details, contact the support team.
244.x.x.xERR_GRID_INTEG_POC_NOT_MULTIPLEInternal error. For more details, contact the support team.
245.x.x.xERR_GRID_INTEG_POC_SMALL_FRAGInternal error. For more details, contact the support team.
246.x.x.xERR_POC_FWD_COBRA_FIRSTFRAG_ERRORInternal error. For more details, contact the support team.
247.x.x.xERR_DEVPOPSInternal error. For more details, contact the support team.
248.x.x.xERR_MANIFEST_MANIPULATION_MASTER_NO_STREAMInternal error. For more details, contact the support team.
249.x.x.xERR_DCVFast Domain Control Validation encountered an error during the communication with DcvManager.
250.x.x.xERR_FWD_CONTENT_SHA256Internal error. For more details, contact the support team.
251.x.x.xERR_HRS_SPACE_AT_HDR_NAME_STARTPossible request smuggling detected. There is a space at the start of header name of a request.
252.x.x.xERR_HRS_STRICT_MODE_HTTP_HDR_PARSINGRequest interrupted due to violating the strict mode in HTTP header parsing.
253.x.x.xERR_HRS_UNAMBIGUOUS_MODE_HTTP_HDR_PARSINGRequest interrupted due to violating unambiguous mode in HTTP header parsing.
254.x.x.xERR_HRS_FOLDED_LINE_ABORTRequest interrupted due to folded line detection in header.
255.x.x.xGET_FILTERED_OBJInternal error. For more details, contact the support team.

Did this page help you?