What is difference between Map() and MapGet() methods middleware?

Question

In .NET Core middleware components what is the difference between Map() methods and MapGet() methods.

Jaimin Shethiya · Answer

Hello Fozle, Method MapGet: Goal: MapGet is specifically made to handle GET requests from HTTP requests. It is employed to specify endpoints that only react to GET requests. Use: MapGet is usually used to receive data from the server without changing its state. Examples of this kind of usage include retrieving an item's details or a list of items. Method Map: Goal: Map responds to all kinds of HTTP queries, including GET, POST, PUT, DELETE, and others. Use: Map is used when you need to configure endpoints that have the ability to handle several HTTP request types or when you have custom logic to identify which kind of request needs to be handled. Thanks

Vikas Singh · Answer

Map() Method : This method is used to branch the pipeline based on a route prefix or a route pattern. It's more general-purpose and allows you to specify a condition based on the request path. MapGet() Method : This method specifically handles HTTP GET requests. It's a shorthand method to route HTTP GET requests to a particular middleware, typically used for serving static files or handling specific endpoints that only accept GET requests. Below is an example to explain the difference between the two methods: using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Hosting; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.DependencyInjection; using Microsoft.Extensions.Hosting; namespace MiddlewareExample { public class Startup { public void ConfigureServices(IServiceCollection services) { // Configuration of services, if any } public void Configure(IApplicationBuilder app, IWebHostEnvironment env) { if (env.IsDevelopment()) { app.UseDeveloperExceptionPage(); } // Use MapGet() to handle GET requests for a specific endpoint app.MapGet("/hello", async context => { await context.Response.WriteAsync("Hello World!"); }); // Use Map() to handle requests based on a route prefix app.Map("/admin", adminApp => { adminApp.Use(async (context, next) => { // Middleware specific to the admin route // For example, authentication checks await next.Invoke(); }); adminApp.Run(async context => { await context.Response.WriteAsync("Admin Dashboard"); }); }); // Default middleware for other requests app.Run(async context => { await context.Response.WriteAsync("Default Middleware"); }); } } } In this example: MapGet ("/hello", ...) will handle only HTTP GET requests to the "/hello" endpoint. Map ("/admin", ...) will branch the pipeline for requests with paths starting with "/admin", allowing you to apply specific middleware only for these routes. The Run () method at the end serves as a fallback for requests that do not match any previous middleware. So, to summarize, Map() is used for more general routing purposes, while MapGet() is specifically for handling GET requests.