http error 400 in catalog
Please let the programmers know that the catalog is giving http error 400 messages in searches. Since this is the only place I'm getting that message, I'm pretty sure it's something in the catalog. If it's a known problem, carry on and ignore this. 😀
Livingston, Michigan>Land Records>First request went to the http error 400
Livingston, Michigan>Land Records>Second request went to "We are unable to display search results due to technical difficulties. Please try searching again in a few minutes."
Could you please provide the exact search path you took to the Land Records from Livingston, Michigan, which gave you the error 400 message?
We went to the catalog page and entered the following location for our search: United States, Michigan, Livingston. We also opened a keyword field and entered: Land Records. When we clicked to do the search, the results provided the following page and we clicked on each title to open the specific collections that were mentioned in the results that we generated, therefore, we did not experience the problem you have described.
The following information from a Google search describes what causes a 400 error...
"A 400 Bad Request Error occurs when a request sent to the website server is incorrect or corrupt, and the server receiving the request can't understand it."
It may be that because you did not list the location with the country, then the state, then the city that the system did not understand the location.
Sometimes errors occur because of a large cache of temporary files and cookies that hinder your browser's ability to complete your commands. If you have not done so recently, please clear your temporary files as described in the following knowledge article. You may also want to check your browser version since FamilySearch only supports the most current and one previous version of Chrome, Firefox, Edge, and Safari.
You are welcome to share additional information about your search path, and if it is different than the one we have described, we invite you to give this search a try to see if you can find the collections we have posted in our screen shot.1
Clearing the cache using your link worked. I had cleared my cache using the browser, but it evidently missed something!
Many thanks. It was very frustrating.