Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust url length limit threshold in chaise #387

Open
3 tasks
karlcz opened this issue Dec 8, 2022 · 1 comment
Open
3 tasks

Adjust url length limit threshold in chaise #387

karlcz opened this issue Dec 8, 2022 · 1 comment
Assignees

Comments

@karlcz
Copy link
Contributor

karlcz commented Dec 8, 2022

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.

  • Make the threshold a configurable chaise-config variable
  • Determine a suitable threshold for the CFDE deployment scenario (it may come from ELB or other middleware?)
  • Customize this variable in our deployed config for chaise
@karlcz
Copy link
Contributor Author

karlcz commented Dec 8, 2022

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants