-
Notifications
You must be signed in to change notification settings - Fork 0
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
URL parameters can get too long, results in HTTP 431 error #47
Comments
Maybe that's only a problem on my local test environment, where Europarl was imported per component and not per year... |
Apparently URIs should not be longer than 2000 characters, which means that the number of components is quite limited... Some components have slugs of more than 30 characters, which means a maximum number of selected components of 50 or so. I'm not really sure what we should do with this. Limit the size of component IDs and the number of selected components? Or use different component identifiers (e.g. numbers)? |
One thing we could do is use a shorter encoding scheme for the (probably common) case where you select a full treebank |
If we switch to numerical component IDs, we could also compress the selection with ranges of consecutive ids. |
Sounds good! Luckily the components already have a number as their primary key, so it will be an easy switch :) (That is because component slugs do not have to be unique.) |
The problem also occurs when the XPath query is very large. I tried selecting the MWE "de kat uit de boom kijken" with the Europarliament corpus and then refreshed the page, which failed. |
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/431
The text was updated successfully, but these errors were encountered: