Multiple retry on Serverless Lambda Functions with 404 statusCode

ndr4 · August 3, 2021, 7:33am

When I return a statusCode of 404 with a serverless function I see the system retry and call again the functions 4 times.

For example if this URL return a 404

http://localhost:8888/.netlify/functions/getproduct/57498375

In the logs I see the function has been called 4 times

http://localhost:8888/.netlify/functions/getproduct/57498375.htm
http://localhost:8888/.netlify/functions/getproduct/57498375.html
http://localhost:8888/.netlify/functions/getproduct/57498375/index.html
http://localhost:8888/.netlify/functions/getproduct/57498375/index.htm

At first, I thought it was the browser, but then I saw that all the browsers have the same behaviour.
I cannot find anything in the Netlify documentation nor the AWS Lambda Functions docs.

Does somebody know who is responsible for these calls? And also know how to stop them?

coelmay · August 3, 2021, 8:31am

No one, as in no person, is responsible for the calls. They are from the alternativePathsFor function in @netlify/cli/src/utils/proxy.js

I don’t believe you can.

ndr4 · August 3, 2021, 8:49am

Aahah, sorry I meant what system is responsible - browser, lambda functions, netrlify dev, …

That is a shame.

coelmay · August 3, 2021, 8:53am

Unsure why you (apparently) find this such an issue.

ndr4 · August 3, 2021, 9:19am

For debugging purpose I would like to have only one answer instead of 4.
Plus, in my opinion, it should be customizable: I should decide which are the alternativePaths of my API.

coelmay · August 3, 2021, 9:31am

github.com/netlify/cli

Netlify dev tries to resolve to a page when returning 404 from a function

opened 10:08PM - 16 Oct 20 UTC

closed 03:56PM - 15 Aug 22 UTC

ercgrat

type: bug area: functions area: command: dev

**Describe the bug** I have a FaunaDB CRUD API that I updated to pass on the …exact HTTP status code from the database request so that I could catch 404 errors on the client. When my function returns 404, something (not my client code, probably netlify middleware - I checked the Network log in Chrome) initiates another function request that tacks on '.html' to my API route. Snippet of the output: ``` Request from ::1: GET /.netlify/functions/cart/279578027748229641 . . . Response with status 404 in 204 ms. // This is the 404 that is correctly returned Request from ::1: GET /.netlify/functions/cart/279578027748229641.html // A request to the same route plus '.html' follows immediately ``` This causes errors in code which is expecting numeric input for the id. It also forces me to return a non-404 error. **To Reproduce** Steps to reproduce the behavior: 1. Create a function that returns a 404 error 2. Execute the function in netlify dev 3. Observe the above behavior **Configuration** Here's my actual function code: ``` /* Import faunaDB sdk */ const faunadb = require('faunadb'); const q = faunadb.query; const client = new faunadb.Client({ secret: process.env.FAUNA_DB_SECRET, timeout: 30 }); exports.handler = async event => { const id = event.id; console.log(`Function 'read' invoked. Read id: ${id}`) return client .query(q.Get(q.Ref(q.Collection('carts'), id))) .then(response => { console.log('success', response) return { statusCode: 200, body: JSON.stringify(response), } }) .catch(error => { console.log('error', error) return { statusCode: error.requestResult.statusCode, body: JSON.stringify(error), } }); } ``` **Expected behavior** The 404 error gets returned to the client. **CLI Output** See problem description.