Open karlcz opened 1 year ago
When a sufficiently large set of choices is "submitted" from the facet multi-picker, the recordset app fails with:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>
which we think is coming from some middleware/service container layer before it reaches the actual /ermrest/ service.
This is a pretty pathological test case, where upwards of 500 choices have been selected across several facets. But, since chaise has a mechanism meant to stop the user without breaking the app, we should try to adjust the limits to make it work as designed...
Chaise has a built-in heuristic to warn the user when too many facet choices would cause the backend query URLs to exceed a length limit. However, it seems like errors are reached in the CFDE deployment before this threshold is reached.