B Error Code Generated by SCP

This section describes HTTP error responses generated by SCP:

Table B-1 SCP Generated Error Responses

HTTP Status Code	Sample Error Scenarios at SCP
400	When SCP receives a request with malformed URL (For example, % is added URL after apiRoot).
400 Not Found	When SCP receives request with the 3gpp-sbi-routing-binding header and an invalid version.
400 Bad Request	When SCP receives a request with the malformed 3GPP-SBI-routing-binding header.
411 Length Required	Not Applicable
413 Payload Too Large	Not Applicable
429 Too Many Requests	When the ingress rate exceeds the configured limit for a given consumer, SCP rejects the additional messages with the error code.
431 Request Header Fields Too Large	When SCP receives a request with the total length of the headers are larger than 8k.
500 Internal Error	Sample 1: When payload size content length exceeds the 256 KB threshold limit. Sample 2: When the response is bigger than configured. maxPayloadSizeInKb. Sample 3: When SCP receives a request with incorrect content-length header field.
503 NF_CONGESTION	Sample 1: When the producer is overloaded and no alternates are available. Sample 2: When the SCP is overloaded based on configured thresholds.
503 Service Unavailable	When SCP receives a request with the 3gpp-sbi-routing-binding header and an invalid API name.
504 Gateway Timeout	When no response is received from a producer for the configured response timeout value.
508 Loop Detected	When SCP receives a via header with its own FQDN or IP.