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

DataTables warning/Ajax error (Pywb Replay) #1096

Open PedroG1515 opened 3 years ago

PedroG1515 commented 3 years ago

What is the URL that originated the issue? https://arquivo.pt/wayback/20210317114147/http://www.pdesenvolvimento.pt/oportunidades-e-candidaturas/quadro-geral?setor=Tecnologias%20de%20Informa%C3%A7%C3%A3o

What happened? Pop up with the mensage:

_DataTables warning: table id=table_feedsite - Ajax error. For more information about this error, please see http://datatables.net/tn/7

VascoRatoFCCN commented 1 year ago

The website is trying to dynamically load data from a database but it's getting a 500 reply. It's strange that the reply isn't a 404, especially because when we try to access the request directly, we get a 404.

Maybe the request headers impact whether the reply is a 500 or a 404? Could this be a faulty crawl and we're replaying the recorded 500 reply?