I've set up a .net core application with umbraco 9 and created an api controller. I want to use a different app to hit the api endpoint but I receive this message:
System.InvalidOperationException: Endpoint UmbracoNine.Controllers.HomeController.GetHomeHeading (UmbracoNine) contains CORS metadata, but a middleware was not found that supports CORS.
Configure your application startup by adding app.UseCors() inside the call to Configure(..) in the application startup code. The call to app.UseCors() must appear between app.UseRouting() and app.UseEndpoints(...).
at Microsoft.AspNetCore.Routing.EndpointMiddleware.ThrowMissingCorsMiddlewareException(Endpoint endpoint)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext)
at Umbraco.Cms.Web.Website.Middleware.PublicAccessMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>cDisplayClass6_1.<1>d.MoveNext()
I followed the instructions by creating a cors policy in the startup.cs configure services:
and calling app.UserCors(corsPolicy) in the startup.cs configure. But I still receive the same message on the api controller. How can I fix this in .net core with umbraco 9 api controller?
The key part is The call to app.UseCors() must appear between app.UseRouting() and app.UseEndpoints(...). Umbraco makes both those calls for you, so you can't just add the UseCors() call directly to the Startup.cs file, otherwise it won't appear between those two calls.
Fortunately Umbraco does offer the IUmbracoPipelineFilter interface to handle cases such as this. It lets you tap into the startup pipeline between key points. There isn't any documentation I could find, but when adding CORS to the v9 version of the GraphQL package, I was able to work through it enough to get it working.
What you do is add a class that extends UmbracoPipelineFilter and implement the PostPipeline method to make the call. You can see an example of that here. You'll need to add an IConfigureOptions<UmbracoPipelineOptions> implementation to register you filter, as seen here. Then you'll need to reference that class in the service registration using the ConfigureOptions extension method, as seen here.
Finally, if you want to customize the policy at all, you will also need to add your CORS policy before the UseCors call, either in a composer or earlier in the Startup method. More details on that can be find in the Microsoft documentation.
hello - i would like to dynamically set some response headers using the umbraco context of the current page. Is middleware (and the above technique) the best/simplest way of doing this? i.e. middleware to hook into the umbraco published content context.
Enable cors on umbraco 9
I've set up a .net core application with umbraco 9 and created an api controller. I want to use a different app to hit the api endpoint but I receive this message:
System.InvalidOperationException: Endpoint UmbracoNine.Controllers.HomeController.GetHomeHeading (UmbracoNine) contains CORS metadata, but a middleware was not found that supports CORS. Configure your application startup by adding app.UseCors() inside the call to Configure(..) in the application startup code. The call to app.UseCors() must appear between app.UseRouting() and app.UseEndpoints(...). at Microsoft.AspNetCore.Routing.EndpointMiddleware.ThrowMissingCorsMiddlewareException(Endpoint endpoint) at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext) at Umbraco.Cms.Web.Website.Middleware.PublicAccessMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>cDisplayClass6_1.<1>d.MoveNext()
I followed the instructions by creating a cors policy in the startup.cs configure services:
services.AddCors(options => { options.AddPolicy(corsPolicy, builder => { builder.AllowAnyOrigin() .AllowAnyMethod() .AllowAnyHeader(); }); });
and calling app.UserCors(corsPolicy) in the startup.cs configure. But I still receive the same message on the api controller. How can I fix this in .net core with umbraco 9 api controller?
The key part is
The call to app.UseCors() must appear between app.UseRouting() and app.UseEndpoints(...). Umbraco makes both those calls for you, so you can't just add the UseCors() call directly to the Startup.cs file, otherwise it won't appear between those two calls.Fortunately Umbraco does offer the
IUmbracoPipelineFilterinterface to handle cases such as this. It lets you tap into the startup pipeline between key points. There isn't any documentation I could find, but when adding CORS to the v9 version of the GraphQL package, I was able to work through it enough to get it working.What you do is add a class that extends
UmbracoPipelineFilterand implement thePostPipelinemethod to make the call. You can see an example of that here. You'll need to add anIConfigureOptions<UmbracoPipelineOptions>implementation to register you filter, as seen here. Then you'll need to reference that class in the service registration using the ConfigureOptions extension method, as seen here.Finally, if you want to customize the policy at all, you will also need to add your CORS policy before the UseCors call, either in a composer or earlier in the Startup method. More details on that can be find in the Microsoft documentation.
That worked! Thank you so much for the help
Finally, I have had solved the CORS problem. I make the record one here.
not works and makes the whole site down
i am using umbraco 11
hello - i would like to dynamically set some response headers using the umbraco context of the current page. Is middleware (and the above technique) the best/simplest way of doing this? i.e. middleware to hook into the umbraco published content context.
thanks
NB I found my way here via a blog post from Andy - https://www.andybutland.dev/2022/05/customising-umbraco-pipeline.html I just wonder if i should be nervous about using this pipeline approach given that its not in the official docs anywhere?
i followed Paul Seal and works fine
https://codeshare.co.uk/blog/how-to-send-emails-in-umbraco-9-using-iemailsender/
is working on a reply...