-
Notifications
You must be signed in to change notification settings - Fork 16
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
Error when viewing records with many holdings #1619
Comments
Does this still happen? I was never able to trigger it. |
Yes it is happening right now with https://muscat.rism.info/admin/sources/852028308! |
How often does it happen? I can't seem to reproduce it, not even if I storm muscat with refreshes... |
When it happens open up the web inspector in Chrome and take a screenshot of any errors in the console. 403 would suggest that some credentials are not being sent.. maybe a CORS or some cross-origin problem where a cookie can’t be sent to a different url? |
I wonder if it is the SBB proxy blowing up, I can't find 403s in the logs in muscat and depending from the connection I'm using (eduroam, RISM wifi or VPN) I get this error always (eduroam) or never (VPN) |
@MFalletta and I have encountered this error when viewing records that have dozens of holdings:
In German it looks like this:
It is happening right now with https://muscat.rism.info/admin/sources/1001299207 and https://muscat.rism.info/admin/sources/852028308 -- Windows 10, Chrome. These are both treatises.
I think https://muscat.rism.info/admin/sources/990053593 holds the record for most holdings, but it is not triggering the error right now.
The text was updated successfully, but these errors were encountered: