Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Access denied or empty body

Aberta
  • Algo errado?
#209 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
javascript, node.js, redis
Domínio
backend

Direção de pesquisa

Start by reproducing the 403 or empty-body response with the shown prerender-node middleware, comparing requests with and without the Googlebot user agent. Inspect the beforeRender and afterRender hooks, Redis cache behavior, and the /render?url=https://www.google.com/ path. Done means identifying the failure and restoring a non-empty response with useful error logging.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Issue: HTTP ERROR 403 - Access denied.
Issue appears during last 3 days, before everything was working fine.

Setup:

  • Server is Linux Ubuntu
  • Local prerender under Node, which is working fine, can access page: /render?url=https://www.google.com/
  • "prerender-node" setup with Redias cache.
  • Assessing website by browsing with googlebot in User agent string.

Deep dive into testing:

  • Website is accessible without googlebot in User agent string.
  • In afterRender event getting empty body for any request url
  • In afterRender error object is null
  • Redis cache is working, even when removing cache mechanism fully, issue persist
  • Files permission is correct and was not changed.
  • When removing app.use(prerender); website again accessible with googlebot in User agent string.
  • Version of packages including "prerender-node" was not released, so nothing to update
  • Version of "google-chrome-stable" checked and updated to latest one - 92.0.4515
  • Reason of this all points is not applicable: [https://docs.prerender.io/article/25-empty-or-partially-rendered-pages](Empty or partially rendered pages) as it is working with url /render?url=https://www.google.com/
  • pageDoneCheckInterval increased up to 20sec to make sure it is not a reason
  • Getting empty body immediately, some some error is happening there, but no any error log, as I have pageDoneCheckInterval: 5000, I should get response in 5 sec, which is not happening.

Ideas what can be a reason:

  • Something got broken in process of Prerender in some dependencies.
  • There is some limit of requested pages per month, but as I use Prerender locally, as I understood it is not limited somehow.
  • Some another crazy reason))

Code prerender section for any case:

// Setup prerender
prerender = require('prerender-node');
prerender.set('protocol', 'https');
prerender.crawlerUserAgents.push('Validator.nu/LV');
prerender.crawlerUserAgents.push('W3C-checklink');
app.use(prerender);

// Setup redis cache
var redis = require("redis"),
	client = redis.createClient();

client.flushdb( function (err, succeeded) {
});

prerender.set('beforeRender', function(req, done) {
	client.get(req.url, done);
}).set('afterRender', function(err, req, prerender_res) {
  if ( prerender_res ) {
    client.set(req.url, prerender_res.body)
  }
});

Anyway this was working previously very long and very stable.

Any idea will appreciated, thanks in advance.

Linguagem predominante
JavaScript
Estrelas
921
Forks
184
Nenhum PR com merge em 30d

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de prerender/prerender-node

Todas as issues de prerender/prerender-node

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.