Weird server reply
The server sent a response that curl could not parse.
8
8
Echo Request
Requests that the recipient return an Echo Reply (type 0) with the same data payload. The basis of the ping utility for connectivity testing.
References
strongerAuthRequired
The server requires stronger authentication than was provided to perform the requested operation. The client must bind using a stronger authentication method.
MEMORY_PARITY_ERROR
The server detected a parity error in the memory when attempting to read extended memory or record file. The client may retry the request; however the parity error will likely persist until the device is serviced.
Numeric value: 8
Symbolic codes with this numeric value
- CONNECTION_TIMEOUT Connection Timeout bluetooth
- DUPLICATE_COLUMN Duplicate column clickhouse
- NXRRSET RR set that should exist does not dns
- RESOURCE_EXHAUSTED Resource exhausted gcp
- RESOURCE_EXHAUSTED Resource exhausted grpc
- CANCEL Cancel http2
- QUIC_TRANSPORT_PARAMETER_ERROR Transport parameter error http3
- BROKER_NOT_AVAILABLE Broker Not Available kafka
- KDC_ERR_PRINCIPAL_NOT_UNIQUE Multiple principal entries in database kerberos
- 8 MEMORY_PARITY_ERROR modbus
- E_NOTICE Runtime Notice php
- ENOEXEC Executable file format error posix
- wrongLength Wrong Length snmp
- SQLITE_READONLY Read-only database sqlite
- SSH_DISCONNECT_PROTOCOL_VERSION_NOT_SUPPORTED Protocol Version Not Supported ssh
- ERROR_NOT_ENOUGH_MEMORY Not enough memory windows
- ENOEXEC Exec format error windows-errno