<\/div>\n

Merhaba,<\/p>\n

Malumunuz, Asp.NET Core uygulamalar\u0131n\u0131 geli\u015ftirirken lalettayin bir URL kullanamamakta, IPv4 ve IPv6 i\u00e7in loopback adresi e\u015fli\u011finde http:\/\/localhost:5000<\/em>, http:\/\/127.0.0.1:5000<\/em> veya http:\/\/[::1]:5000<\/em> formatlar\u0131nda url’ler kullan\u0131labilmekte ya da geli\u015ftirmenin yap\u0131ld\u0131\u011f\u0131 makinede bulunan belirli bir IP adresi \u00fczerinden de(misal olarak http:\/\/192.168.1.12:1453)<\/span> kullan\u0131m s\u00f6z konusu olabilmektedir. Bunlar\u0131n d\u0131\u015f\u0131nda belirli bir port \u00fczerinden de herhangi bir IP adresi http:\/\/*:1461<\/em> misali kullan\u0131labilmektedir. Bu kal\u0131plar\u0131n hangisinin kullan\u0131laca\u011f\u0131 iste\u011fe ba\u011fl\u0131 olabilir lakin uygulamada hangi format\u0131n kullan\u0131laca\u011f\u0131 taraf\u0131m\u0131zca bildirilmesi gerekmektedir. \u0130\u015fte bu i\u00e7eri\u011fimizde bunu s\u00f6ylemenin yedi farkl\u0131 yolunu inceleyece\u011fiz. O halde buyurun ba\u015flayal\u0131m…<\/p>\n

\n
UseUrls()<\/em><\/strong>
\nURL ayarlamak i\u00e7in en kolay y\u00f6ntem UseUrls metodudur diyebiliriz.<\/p>\n
\n
\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.WebHost.UseUrls("http:\/\/localhost:1453", "https:\/\/localhost:1461");\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/", () => "Merhaba D\u00fcnya...");\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\n
Asp.NET Core 1.0 s\u00fcr\u00fcm\u00fcnden beri kullan\u0131lan bir y\u00f6ntemdir.\n<\/li>\n
WebApplication.Urls & WebApplication.Run()<\/em><\/strong>
\nBu y\u00f6ntemde de WebApplication<\/code> nesnesi \u00fczerinden uygulama taraf\u0131ndan dinlenecek url’ler belirlenebilmektedir.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/", () => "Merhaba D\u00fcnya...");\r\n\r\napp.Urls.Add("http:\/\/localhost:1453");\r\napp.Urls.Add("https:\/\/localhost:1461");\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\nBenzer \u015fekilde WebApplication<\/code> nesnesinin Run<\/code> metodu \u00fczerinden de uygulama url’i belirlenebilmektedir.<\/p>\n \n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/", () => "Merhaba D\u00fcnya...");\r\n\r\napp.Run("https:\/\/*:1453");\r\n<\/pre>\n<\/div>\nTabi Run<\/code> metodu e\u015fli\u011finde tek bir url’in belirlenebilece\u011fini s\u00f6ylemekte fayda vard\u0131r. Bu nedenle birden fazla url’in ayarlanmas\u0131 gereken durumlarda di\u011fer y\u00f6ntemlere ba\u015fvurulmas\u0131 gerekmektedir.\n<\/li>\n URL \u0130\u00e7in Environment Variables<\/em><\/strong> \nAsp.NET Core mimarisinde URL belirlerken genellikle uygulaman\u0131n farkl\u0131 ortamlarda farkl\u0131 URL’ler kullanabilece\u011fi \u015fekilde ayarlanmas\u0131 gerekebilir. URL’leri environment variables olarak ayarlamak, uygulaman\u0131n ta\u015f\u0131nabilirli\u011fini art\u0131rabilir ve birden \u00e7ok ortamda \u00e7al\u0131\u015fmas\u0131n\u0131 kolayla\u015ft\u0131rabilir. Kullan\u0131m\u0131 a\u015fa\u011f\u0131daki gibi i\u015fletim sistemine g\u00f6re farkl\u0131l\u0131k arz edebilir.<\/p>\nWindows i\u015fletim sisteminde CMD veya PowerShell i\u00e7in;<\/p>\n \n\r\nsetx ASPNETCORE_URLS "http:\/\/localhost:1453"\r\n<\/pre>\n<\/div>\nWindows i\u015fletim sisteminde PowerShell i\u00e7in;<\/p>\n \n\r\n$Env:ASPNETCORE_URLS="http:\/\/localhost:1453"\r\n<\/pre>\n<\/div>\nUnix tabanl\u0131 i\u015fletim sistemlerin(Linux, macOS vs.) i\u00e7in;<\/p>\n \n\r\nexport ASPNETCORE_URLS="http:\/\/localhost:1454;https:\/\/localhost:1461"\r\n<\/pre>\n<\/div>\n<\/li>\nCommand Line Arguments<\/em><\/strong> \nAsp.NET Core mimarisinin yap\u0131land\u0131rma sisteminde url’i belirlemenin bir ba\u015fka yolu da command line’dan ge\u00e7mektedir. \u015e\u00f6yle ki;<\/p>\n\n\r\ndotnet run -- --urls "http:\/\/localhost:1453"\r\n<\/pre>\n<\/div>\nya da<\/p>\n \n\r\ndotnet run -- --urls "http:\/\/*:1453;http:\/\/localhost:1461"\r\n<\/pre>\n<\/div>\nAyr\u0131ca a\u015fa\u011f\u0131daki gibi --http_ports<\/code> ve --https_ports<\/code> se\u00e7enekleri de kullan\u0131labilir.<\/p>\n \n\r\ndotnet run -- --http_ports "1453;1461" --https_ports "1915;1921"\r\n<\/pre>\n<\/div>\n<\/li>\nappsettings.json<\/em><\/strong> \nappsettings.json<\/code> ve ortama \u00f6zg\u00fc appsettings.Development.json<\/code> ve appsettings.Production.json<\/code> gibi varyasyonlar\u0131, Asp.NET Core yap\u0131land\u0131rmas\u0131nda olduk\u00e7a kolay bir yap\u0131land\u0131rma imkan\u0131 sa\u011flamaktad\u0131r. A\u015fa\u011f\u0131daki gibi pratik bir \u015fekilde url tan\u0131mlamas\u0131 yap\u0131labilmektedir.<\/p>\n\n\r\n{\r\n "urls": "http:\/\/*:1453",\r\n "Logging": {\r\n "LogLevel": {\r\n "Default": "Information",\r\n "Microsoft.AspNetCore": "Warning"\r\n }\r\n },\r\n "AllowedHosts": "*"\r\n}\r\n<\/pre>\n<\/div>\n<\/li>\nlaunchSettings.json<\/em><\/strong> \nAsp.NET Core uygulamas\u0131n\u0131 development s\u00fcrecinde aya\u011fa kald\u0131r\u0131rken, \u00f6nceden tan\u0131mlanm\u0131\u015f \u00e7e\u015fitli url ve port bilgilerinin bulundu\u011fu profiller e\u015fli\u011finde \u00e7al\u0131\u015fma yapmam\u0131z\u0131 sa\u011flayan launchSettings.json<\/code> dosyas\u0131 da konumuzun geleneksel \u00e7\u00f6z\u00fcm\u00fcn\u00fc bizlere sa\u011fl\u0131yor diyebiliriz.<\/p>\n\n\r\n{\r\n "$schema": "http:\/\/json.schemastore.org\/launchsettings.json",\r\n "iisSettings": {\r\n "windowsAuthentication": false,\r\n "anonymousAuthentication": true,\r\n "iisExpress": {\r\n "applicationUrl": "http:\/\/localhost:1494",\r\n "sslPort": 44397\r\n }\r\n },\r\n "profiles": {\r\n "http": {\r\n "commandName": "Project",\r\n "dotnetRunMessages": true,\r\n "launchBrowser": true,\r\n "launchUrl": "swagger",\r\n "applicationUrl": "http:\/\/localhost:5173",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n },\r\n "https": {\r\n "commandName": "Project",\r\n "dotnetRunMessages": true,\r\n "launchBrowser": true,\r\n "launchUrl": "swagger",\r\n "applicationUrl": "https:\/\/localhost:7036;http:\/\/localhost:5173",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n },\r\n "IIS Express": {\r\n "commandName": "IISExpress",\r\n "launchBrowser": true,\r\n "launchUrl": "swagger",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n }\r\n}\r\n<\/pre>\n<\/div>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere profiles<\/code> alt\u0131nda tan\u0131mlanan profiller; ‘http’, ‘https’ ve ‘IIS Express’ olarak nitelendirilmi\u015flerdir. Bizler ek olarak a\u015fa\u011f\u0131daki gibi kendimize \u00f6zg\u00fc bir profil tan\u0131m\u0131nda bulunabilir ve uygulamay\u0131 bu profilin ayarlar\u0131nda aya\u011fa kald\u0131rabiliriz.<\/p>\n \n\r\n{\r\n .\r\n .\r\n .,\r\n "profiles": {\r\n .\r\n .\r\n .,\r\n "CustomProfile": {\r\n "commandName": "Project",\r\n "dotnetRunMessages": true,\r\n "launchBrowser": true,\r\n "applicationUrl": "https:\/\/localhost:1453;http:\/\/localhost:1461",\r\n "environmentVariables": {\r\n "ASPNETCORE_ENVIRONMENT": "Development"\r\n }\r\n }\r\n }\r\n}\r\n<\/pre>\n<\/div>\nAsp.NET Core mimarisinde launchSettings.json<\/code> dosyas\u0131n\u0131n kullan\u0131lmas\u0131 i\u00e7in ekstradan bir \u015fey yap\u0131lmas\u0131na gerek duyulmamakta, uygulama aya\u011fa kald\u0131r\u0131l\u0131rken dosya otomatik olarak alg\u0131lanmaktad\u0131r. \u015e\u00f6yle ki; uygulamay\u0131 dotnet run<\/code> komutu ile \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda uygulama default olarak ‘http’ profili ayarlar\u0131nda aya\u011fa kald\u0131r\u0131lacakt\u0131r. E\u011fer ki var olan profillerden birinde aya\u011fa kald\u0131rmak istiyorsan\u0131z \ndotnet run --launch-profile \"https\"<\/code> \u015feklinde talimat\u0131n verilmesi gerekmektedir. Ee do\u011fal olarak kendi olu\u015fturdu\u011funuz profilde aya\u011fa kald\u0131rabilmek i\u00e7inse \ndotnet run --launch-profile \"CustomProfile\"<\/code> talimat\u0131n\u0131n verilmesi gerekmektedir.<\/p>\n G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere bu dosya sayesinde environment yap\u0131land\u0131rmas\u0131 olduk\u00e7a kolay ve kullan\u0131\u015fl\u0131 bir hale getirilmi\u015ftir. T\u00fcm bu avantajlar\u0131na kar\u015f\u0131n, launchSettings.json<\/code> dosyas\u0131n\u0131 kullanmaks\u0131z\u0131n uygulamay\u0131 aya\u011fa kald\u0131rmak istiyorsan\u0131z \ndotnet run --no-launch-profile<\/code> talimat\u0131n\u0131 verebilirsiniz.\n<\/li>\n KestrelServerOptions.Listen()<\/em><\/strong> \n\u015eimdiye kadar ele ald\u0131\u011f\u0131m\u0131z t\u00fcm yakla\u015f\u0131mlar Kestrel i\u00e7in URL’leri dolayl\u0131 olarak ayarlamaktad\u0131r. T\u00fcm bunlar\u0131n yerine do\u011frudan Kestrel \u00fczerinden de url yap\u0131land\u0131rmas\u0131nda bulunabiliriz.<\/p>\n\n\r\nusing System.Net;\r\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\nbuilder.WebHost.ConfigureKestrel(options =>\r\n{\r\n \/\/-> http:\/\/localhost:1453\r\n options.Listen(IPAddress.Loopback, port: 1453);\r\n \/\/-> http:\/\/*:1461\r\n options.ListenAnyIP(1461);\r\n \/\/-> https:\/\/localhost:1915\r\n options.ListenLocalhost(1915, listenOptions => listenOptions.UseHttps());\r\n \/\/-> https:\/\/*:1921a\r\n options.ListenAnyIP(1921, listenOptions => listenOptions.UseHttps());\r\n});\r\n\r\nvar app = builder.Build();\r\n\r\napp.MapGet("\/", () => "Merhaba D\u00fcnya...");\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\nKestrel’i yukar\u0131daki gibi hard-coded bir \u015fekilde yap\u0131land\u0131rabilece\u011fimiz gibi appsettings.json<\/code> \u00fczerinden de a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rabiliriz.<\/p>\n \n\r\n{\r\n\r\n "Kestrel": {\r\n "Endpoints": {\r\n "HttpLoopback": {\r\n "Url": "http:\/\/localhost:1453"\r\n },\r\n "HttpAny": {\r\n "Url": "http:\/\/*:1461"\r\n },\r\n "HttpsDefaultCert": {\r\n "Url": "https:\/\/localhost:1915"\r\n },\r\n "HttpsInlineCertFile": {\r\n "Url": "https:\/\/*:1921"\r\n }\r\n }\r\n },\r\n "Logging": {\r\n "LogLevel": {\r\n "Default": "Information",\r\n "Microsoft.AspNetCore": "Warning"\r\n }\r\n },\r\n "AllowedHosts": "*"\r\n}\r\n<\/pre>\n<\/div>\nB\u00f6ylece uygulaman\u0131n yap\u0131land\u0131rmas\u0131n\u0131 koddan ba\u011f\u0131ms\u0131z hale getirebilmekteyiz. Ayr\u0131ca bu yap\u0131land\u0131rma yakla\u015f\u0131m\u0131yla ‘Program.cs’ \u00fczerinden ConfigureKestrel<\/code> metodunu \u00e7a\u011f\u0131rmaya gerekte kalmamaktad\u0131r.\n<\/li>\n<\/ol>\n Nihai olarak; \nBu i\u00e7eri\u011fimizde, Asp.NET Core uygulamalar\u0131n\u0131n dinledi\u011fi url’leri ayarlayabilece\u011fimiz yedi farkl\u0131 yolu de\u011ferlendirmi\u015f bulunuyoruz. \u00c7al\u0131\u015fma hayat\u0131nda genel olarak development ortam\u0131 i\u00e7in launchSettings.json<\/code>‘\u0131 kullan\u0131yor olsak da di\u011fer y\u00f6ntemleri bilmek i\u015f s\u00fcre\u00e7lerinde i\u015finize yarayacakt\u0131r kanaatindeyim.<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Malumunuz, Asp.NET Core uygulamalar\u0131n\u0131 geli\u015ftirirken lalettayin bir URL kullanamamakta, IPv4 ve IPv6 i\u00e7in loopback adresi e\u015fli\u011finde http:\/\/localhost:5000, http:\/\/127.0.0.1:5000 veya http:\/\/[::1]:5000 formatlar\u0131nda url’ler kullan\u0131labilmekte ya da geli\u015ftirmenin yap\u0131ld\u0131\u011f\u0131 makinede bulunan belirli bir IP adresi...<\/p>\n","protected":false},"author":1,"featured_media":9596,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3102,4997],"tags":[5035,5034,5033,5037,5036,5038,5030,5032,5031],"class_list":["post-26925","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asp-net-core","category-asp-net-core-8","tag-appsettings-json","tag-command-line-arguments","tag-environment-variables","tag-kestrelserveroptions-listen","tag-launchsettings-json","tag-loopback","tag-useurls","tag-webapplication-run","tag-webapplication-urls"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26925","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=26925"}],"version-history":[{"count":8,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26925\/revisions"}],"predecessor-version":[{"id":26935,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26925\/revisions\/26935"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/9596"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26925"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26925"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26925"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}