301 responses ignored in enqueueLinks

[clemenspeters]

enqueueLinks doesn't work on redirected (301) responses, even though the page content is received.
Is this expected?

My workaround currently:

      async requestHandler({ request, page, enqueueLinks, log }) {
        if (request.url !== request.loadedUrl) {
          log.info(`Detected redirect from ${request.url} to ${request.loadedUrl}`)
          const requestQueue = await RequestQueue.open()
          await requestQueue.addRequest({ url: request.loadedUrl })
        }
        ...
     }

Is there a cleaner way?
Do you find this behaviour intuitive / expected to just ignore 301 pages in enqueueLinks?
Am I missing something?

[B4nan]

We don't ignore 301 redirects. enqueueLinks only adds links to the queue - that is the URL before the redirect, it does not process the request yet. Then the crawler processes requests, and handles redirects normally. request.loadedUrl is the URL after redirects, while request.url is the one before.

I don't understand what you are trying to do with that code sample - you are already inside the request handler with request.loadedUrl, adding it again to the queue would only make the crawler process it again. It was never ignored.