Compatibility with v4?

[josbol]

Hi!

We have been using your attribute on azure functions v3 without issue but when testing on an azure functions project v4 (.NET 6), we immediatly get an 401 error and the following error in the console:

[2022-11-04T18:51:15.280Z] Executed 'Registrar_Lead' (Failed, Id=69f566b5-f755-45c7-92cf-c951c3974f26, Duration=668ms)
[2022-11-04T18:51:15.281Z] System.Private.CoreLib: Exception while executing function: Registrar_Lead. Microsoft.AspNetCore.Server.Kestrel.Core: StatusCode cannot be set because the response has already started.

Any idea what this might cause?

Kinds regards!

[artmasa]

Are you using Isolated or Hosted mode? I have tested in hosted mode without issues. But I think it would not work well with Isolated mode.

[artmasa]

Do you think you might have another filter trying to write to the response on the HttpContext after the authorization filter has changed the status code?
If you are receiving a 401 with a [FunctionAuthorize] decorated and Anonymous HttpTrigger function, it means the Authorization extension is doing it's job, but something else is trying to change the response status again.

I just tested the package with a v4 .NET 6 function and it works just fine. I will commit the v4 sample later.

[josbol]

We are getting this error even when running locally, so I don't think it's a matter running in isolated mode or not, but I'll double check everything to see if there's something odd going in the rest of the Startup code.

…

On Fri, Nov 4, 2022, 19:39 Arturo Martinez ***@***.***> wrote: Do you think you might have another filter trying to write to the response on the HttpContext after the authorization filter has changed the status code? If you are receiving a 401 with a [FunctionAuthorize] decorated and Anonymous HttpTrigger function. it means the Authorization extension is doing it's job, but something else is trying to change the response status again. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADREEAO4XHK3OJSX3N22D4LWGWGANANCNFSM6AAAAAARXO7QUA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[artmasa]

Have created #11 PR adding a v4 sample project

[artmasa]

@josbol, can you send me a list of your public dependencies with some public startup initialization and see if I can reproduce the problem on my side?

[artmasa]

@josbol, I was able to reproduce your error. It was happening when not checking for an already changed response and then executing the default challenge and forbid authorization framework calls. I'm about to merge a PR to fix it. I will produce a new 3.1.2 preview package you might want to try soon and confirm it solves your problem.

[artmasa]

The PR closed the issue. Reopening to wait for your response for confirmation on fixed issue.