arquivo / pwa-technologies

Arquivo.pt main goal is the preservation and access of web contents that are no longer available online. During the developing of the PWA IR (information retrieval) system we faced limitations in searching speed, quality of results, scalability and usability. To cope with this, we modified the archive-access project (http://archive-access.sourceforge.net/) to support our web archive IR requirements. Nutchwax, Nutch and Wayback’s code were adapted to meet the requirements. Several optimizations were added, such as simplifications in the way document versions are searched and several bottlenecks were resolved. The PWA search engine is a public service at http://archive.pt and a research platform for web archiving. As it predecessor Nutch, it runs over Hadoop clusters for distributed computing following the map-reduce paradigm. Its major features include fast full-text search, URL search, phrase search, faceted search (date, format, site), and sorting by relevance and date. The PWA search engine is highly scalable and its architecture is flexible enough to enable the deployment of different configurations to respond to the different needs. Currently, it serves an archive collection searchable by full-text with 180 million documents ranging between 1996 and 2010.
http://www.arquivo.pt
GNU General Public License v3.0
38 stars 7 forks source link

Site recorded with SavePageNow giving error 429 - Too Many Requests #1300

Closed VascoRatoFCCN closed 1 year ago

VascoRatoFCCN commented 1 year ago

I recorded the following website using SavePageNow on my phone: https://www.wamae.org/

It was added to Arquivo.pt some time later, it's available for consulting on https://arquivo.pt/wayback/20220818202323/https://www.wamae.org/

However when trying to access it, there are missing elements:

image

Looking in the devtools we can see that pywb's requests are being blocked with error 429 Too Many Requests:

image

Afterwards if we try to navigate the Arquivo.pt website we are still blocked with error 429:

image

franciscoesteveira commented 1 year ago

Too Many Requests threshold was being triggered by a path of the recorded website which contained "/services". This wrongly matched against a configured QoS rule "/services". Fixed QoS rules to match only against the start of the path string.