You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed this bug because there was a 503 error reporting "the website is under heavy load (queue full)". We checked with PUL and they said we needed to restart the app, which resolved the problem. But the log has a lot of entries with a bing bot crawling the site, hitting the archive page with multiple clusters repeated in the url (like this)
The problem URL is this one: https://prosody.princeton.edu/archive/?cluster=&page=1, which you get to by moving from searching within a cluster to clicking "Search the full archive." Rebecca and I agree that clicking "Search the full archive" should just take you to https://prosody.princeton.edu/archive/. I don't think it's necessary for search terms and parameters to be preserved in this instance, personally, especially if it is substantially more work.
The text was updated successfully, but these errors were encountered:
* Fix link to main archive search from search within cluster
fixes#544
* Mark querystring_replace result as safe to avoid urlencoding
* Simplify cluster fixtures and test
* Simplify test for search sort with clusters
* Test search within cluster appropriately limits works
We noticed this bug because there was a 503 error reporting "the website is under heavy load (queue full)". We checked with PUL and they said we needed to restart the app, which resolved the problem. But the log has a lot of entries with a bing bot crawling the site, hitting the archive page with multiple clusters repeated in the url (like this)
The problem URL is this one: https://prosody.princeton.edu/archive/?cluster=&page=1, which you get to by moving from searching within a cluster to clicking "Search the full archive." Rebecca and I agree that clicking "Search the full archive" should just take you to https://prosody.princeton.edu/archive/. I don't think it's necessary for search terms and parameters to be preserved in this instance, personally, especially if it is substantially more work.
The text was updated successfully, but these errors were encountered: