Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Functions v4 support #934

Open
AndrzejKomarnicki opened this issue Jul 3, 2022 · 9 comments
Open

Azure Functions v4 support #934

AndrzejKomarnicki opened this issue Jul 3, 2022 · 9 comments

Comments

@AndrzejKomarnicki
Copy link

When doing npm run build && func host start I get the following error:

Warning: Proxies are not supported in Azure Functions v4. Instead of 'proxies.json', try Azure API Management: https://aka.ms/AAfiueq

After trying to access the endpoint, for example: https://nestjstest1.azurewebsites.net/api

I get the following error:

Server Error

502 - Web server received an invalid response while acting as a gateway or proxy server.
There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.

Please add Azure Functions v4 support, which has been out since last year.

Reference:

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-functions-v4-versus-v3/ba-p/3276055

@kamilmysliwiec
Copy link
Member

Would you like to create a PR for this feature?

@diberry
Copy link

diberry commented Apr 19, 2023

There is a new v4 runtime for Node.js which makes the programming model more app-centric. It is in preview. I would like to update this package to work with the new programming model but I'm not sure what the previous issue in this thread would mean in terms of creating a pr.

@AndrzejKomarnicki
Copy link
Author

Closing issue, I'm not working on anything Azure related anymore.

@johnykes
Copy link

johnykes commented Nov 5, 2023

After hours of trying different things...

I managed to fix this error by using Azure Functions ~4, but with LINUX (node 18, 32bit).
update: it seems it also worked for Windows, node 20, 64bit.

But only using an old version for azure functions...
"@azure/functions": "^1.0.3",

Hopefully this will help somebody.

Please don't abandon this project 😢

@pigulla
Copy link

pigulla commented Jun 21, 2024

For what it's worth, I've tried to throw money at this problem by contacting Trilon (via the contact form, twice by mail and via Twitter) but received nothing but silence.

As a last-ditch effort, maybe ping @MarkPieszak or @kamilmysliwiec to see if their company actually wants business. And why not ping @henriqueweiand, @delucca, @flamewow, @camilacnery and @mcarballido while I'm at it. All my other efforts to reach out to Trilon have unfortunately utterly failed.

@EtienneDeneuve
Copy link

Hello,

I needed it, so we did it :
https://github.com/Simplifi-ED/azure-func-http/pkgs/npm/azure-func-http

It's almost the same, but updated.

PR and tests are warmly welcomed

@pigulla
Copy link

pigulla commented Jun 21, 2024

Nice! I will take a look at it next week and do some testing.

@pigulla
Copy link

pigulla commented Jun 24, 2024

@EtienneDeneuve, could you publish it to npm? That would make testing it a lot easier (using an alias). Installing it directly from GitHub doesn't contain the dist files so it's kind of a PITA :)

@EtienneDeneuve
Copy link

Sure, I did on https://www.npmjs.com/package/@edeneuve/azure-func-http
But I need to check if it's up to date ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants