HTTP 499 Client Closed Request Error

Main causes

Client intentionally disconnects due to long server response times.
Network issues on the client side causing unintentional disconnections.
Client browser timeout when a request takes too long to complete.
Client-side script cancelling the request before the server can respond.

# Request example 
curl -X POST https://sandbox.oxylabs.io/ -H 'Accept: application/xml;q=0.9' -H 'Accept-Encoding: compress' -H 'User-Agent: Safari/537.36'

Try Scraper API with 5K results

Common fixes

Minimize unnecessary headers and cookies in requests to avoid excessive request overhead.
Shorten the length of the headers by minimizing the size of each header field.
Limit the use of redundant or unnecessary headers in the request.
Configure the server to accept larger header sizes if reduction is not feasible.

# Response example 
HTTP/1.1 499 Client Closed Request
Content-Type: text/plain
Content-Length: 0

Forget HTTP errors with Scraper API

Web scraper API

Self-Service

Public data delivery from a majority of websites

From

Try free for 1 week

Common scraping HTTP error codes

401 Unauthorized	403 Forbidden	404 Not found	405 Method not allowed	406 Not acceptable
407 Proxy authentication required	408 Request timeout	409 Conflict	410 Gone	411 Length required
412 Precondition failed	413 Payload too large	414 Uri too long	415 Unsupported media type	416 Range not satisfiable
417 Expectation failed	421 Misdirected request	422 Unprocessable entity	423 Locked	424 Failed dependency
426 Upgrade required	428 Precondition required	429 Too many requests	431 Request header fields too large	444 Connection: close
451 Unavailable for legal reasons	499 Client closed request	501 Not implemented	503 Service unavailable	505 Http version not supported
506 Variant also negotiates	507 Insufficient storage	508 Loop detected	510 Not extended	511 Network authentication required