HTTP 414 Uri Too Long Error

Main causes

A client improperly converts a POST request to a GET request with long query information.
The client descends into a loop of redirection, such as a redirected URI prefix pointing to a suffix of itself.
The server is under attack by a client attempting to exploit potential security holes.
The client unintentionally or maliciously constructs an excessively long URL.

# Request example 
curl -X GET https://sandbox.oxylabs.io/ -H 'Accept: text/html' -H 'Accept-Encoding: br' -H 'User-Agent: Safari/537.36'

Try Scraper API with 5K results

Shorten the URL by reducing the number of query parameters or the length of each parameter.
Convert the GET request to a POST request to handle larger amounts of data in the request body instead of the URL.
Check and modify server settings to increase the maximum allowable URL length.
Review and correct any redirection loops or misconfigurations causing excessive URL length.

# Response example 
HTTP/1.1 414 URI Too Long
Content-Type: text/html; charset=UTF-8
Content-Length: 49

URI Too Long

Web scraper API

Self-Service

Public data delivery from a majority of websites

From

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