<\/div>\n

Merhaba,<\/p>\n

Bu i\u00e7eri\u011fimizde Azure Function trigger t\u00fcrlerinden ilki ve en \u00e7ok kullan\u0131lan\u0131 olan Http Trigger \u00fczerine detayl\u0131ca konu\u015fuyor olaca\u011f\u0131z.<\/p>\n

Http Trigger Nedir?<\/h3>\n

Http Trigger, taraf\u0131m\u0131za verdi\u011fi endpointler arac\u0131l\u0131\u011f\u0131yla tetiklenebilir bir fonksiyon \u00e7e\u015fididir.<\/p>\n

$\"Http$ <\/a>

Bir \u00f6nceki\u00a0 Azure Function Dosya Yap\u0131s\u0131<\/a> makalemizden \u00f6rnek Http Trigger endpoint g\u00f6rseli…<\/p><\/div>\n

Http Trigger Yap\u0131s\u0131 Nas\u0131ld\u0131r?<\/h3>\n

Http Trigger yap\u0131sal olarak; Route, Query String ve Request Body yap\u0131lanmas\u0131ndan meydana gelmektedir. Bu kavramlar\u0131n izahatlerini yapabilmek i\u00e7in a\u015fa\u011f\u0131daki function’\u0131 ele alal\u0131m;
\nNot! Bu i\u00e7eri\u011fi anlamland\u0131rabilmek i\u00e7in bir Azure Function uygulamas\u0131n\u0131n nas\u0131l olu\u015fturuldu\u011funu bilmeniz gerekmektedir. Bunun i\u00e7in yaz\u0131 dizisi<\/a>ndeki \u00f6nceden kaleme al\u0131nm\u0131\u015f ilgili makalelerden istifade edebilirsiniz.<\/span><\/p>\n

\r\n    public static class MyFunction\r\n    {\r\n        [FunctionName("MyFunction")]\r\n        public static async Task<IActionResult> Run(\r\n            [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] HttpRequest req,\r\n            ILogger log)\r\n        {\r\n            string name = req.Query["name"];\r\n\r\n            string requestBody = await new StreamReader(req.Body).ReadToEndAsync();\r\n            dynamic data = JsonConvert.DeserializeObject(requestBody);\r\n\r\n            return new OkObjectResult(data);\r\n        }\r\n    }\r\n<\/pre>\n\nRoute<\/strong>
\nYukar\u0131daki uygulamay\u0131 aya\u011fa kald\u0131rd\u0131\u011f\u0131m\u0131zda bizlere a\u015fa\u011f\u0131daki endpoint’i verecektir.
\n<\/a>
\nBu endpoint’te ki ‘\/api\/MyFunction<\/span>‘ k\u0131rm\u0131z\u0131yla vurgulanan nokta 3. sat\u0131rdaki ‘[FunctionName(“MyFunction”)]’ attribute’u sayesinde gelmektedir. ‘Run’ fonksiyonunun ‘HttpRequest’ t\u00fcr\u00fcnden olan ‘req’ isimli parametresinin i\u015faretlendi\u011fi ‘HttpTrigger’ attribute’unun ‘Route’ parametresine odaklan\u0131rsan\u0131z e\u011fer, bu parametre bo\u015f oldu\u011fu s\u00fcrece varsay\u0131lan olarak endpoint ismini ‘FunctionName’ attribute’undan alacakt\u0131r.<\/p>\n‘FunctionName’ attribute’unun de\u011feri de\u011fi\u015ftirilirse endpoint a\u015fa\u011f\u0131da g\u00f6rece\u011finiz \u00fczere de\u011fi\u015fmi\u015f olacakt\u0131r.
\n<\/a><\/p>\n
Benzer mant\u0131kla ‘Route’ parametresine girilen de\u011fer ‘FunctionName’i ezecek ve endpoint’i belirleyecektir.
\n<\/a><\/p>\n
Route Parametre Tan\u0131mlama<\/em>
\nKlasik Asp.NET Core uygulamalar\u0131ndaki gibi s\u00fcsl\u00fc parantezler e\u015fli\u011finde olu\u015fturulan function’lara da route parametresi eklenebilmektedir. \u00d6rne\u011fin;
\nmyexample\/{param1}<\/span>\/{param2}<\/span><\/strong><\/em><\/code><\/p>\n
Tan\u0131mlanan bu route parametre de\u011ferlerini yakalayabilmek i\u00e7in function’da o parametre isimlerine kar\u015f\u0131l\u0131k parametrelerin tan\u0131mlanmas\u0131 gerekmektedir. \u015e\u00f6yle ki;
\n<\/a>\n<\/li>\n
Query String<\/strong>
\nEndpoint’ler, parametre alarak gizli bir \u015fekilde de\u011fer ta\u015f\u0131yabilen yap\u0131lar olsada yer yer url \u00fczerinden g\u00fcvenlik gerektirmeyen bilgilerimizi herhangi bir gizlili\u011fe gerek duymaks\u0131z\u0131n de\u011fi\u015fkenler ile ta\u015f\u0131mak isteyebiliriz. Bunun i\u00e7in query string yap\u0131s\u0131 kullan\u0131l\u0131r.<\/p>\nQuery String yap\u0131lanmas\u0131nda, ne ‘Route’ alan\u0131nda s\u00fcsl\u00fc parantez ne de fonksiyonda bir parametre tan\u0131mlamaya gerek vard\u0131r. Direkt olarak url \u00fczerinden tasarlanan query string de\u011ferlerine ‘req’ parametresinin ‘Query’ property’si \u00fczerinden eri\u015fim sa\u011flanabilmektedir.<\/p>\n\u00d6rne\u011fin;
\n<\/a>\n<\/li>\n
Request Body<\/strong>
\nHttp Trigger, client’tan ald\u0131\u011f\u0131 body ile etkile\u015fimli bir tetikleyici sunmaktad\u0131r. G\u00f6nderilen body Stream olarak ‘req.Body’ komutu ile yakalanabilmektedir.<\/p>\nGelen Stream data’y\u0131 a\u015fa\u011f\u0131daki gibi parse ederek kullanabilirsiniz.<\/p>\n\r\n            string requestBody = await new StreamReader(req.Body).ReadToEndAsync();\r\n            dynamic data = JsonConvert.DeserializeObject(requestBody);\r\n<\/pre>\n<\/li>\n<\/ul>\nHttp Trigger CORS Ayarlamas\u0131<\/h3>\nBir endpoint’i t\u00fcketecek kaynak e\u011fer ki bir taray\u0131c\u0131 ise CORS \u00f6zelli\u011fini ayarlamam\u0131z gerekmektedir. Bknz : Asp.NET Core Uygulamalar\u0131nda CORS(Cross-Origin-Resource-Sharing) Politikas\u0131 Ayarlama<\/a><\/span><\/p>\n
CORS; bir g\u00fcvenlik de\u011fil, taray\u0131c\u0131lar i\u00e7in var olan g\u00fcvenli\u011fi gev\u015fetme y\u00f6ntemidir.<\/em><\/p><\/blockquote>\n
Azure Function CORS politikalar\u0131n\u0131 ayarlayabilmek i\u00e7in ‘local.setting.json’ dosyas\u0131na a\u015fa\u011f\u0131daki ifadeyi eklemeniz gerekmektedir.<\/p>\n
\r\n  "Host": {\r\n    "CORS": "*"\r\n  }\r\n<\/pre>\nDosyan\u0131n tam hali;<\/p>\n
\r\n{\r\n  "IsEncrypted": false,\r\n  "Values": {\r\n    "AzureWebJobsStorage": "UseDevelopmentStorage=true",\r\n    "FUNCTIONS_WORKER_RUNTIME": "dotnet"\r\n  },\r\n  "Host": {\r\n    "CORS": "*"\r\n  }\r\n}\r\n<\/pre>\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, Bu i\u00e7eri\u011fimizde Azure Function trigger t\u00fcrlerinden ilki ve en \u00e7ok kullan\u0131lan\u0131 olan Http Trigger \u00fczerine detayl\u0131ca konu\u015fuyor olaca\u011f\u0131z. Http Trigger Nedir? Http Trigger, taraf\u0131m\u0131za verdi\u011fi endpointler arac\u0131l\u0131\u011f\u0131yla tetiklenebilir bir fonksiyon \u00e7e\u015fididir. Http Trigger...<\/p>\n","protected":false},"author":1,"featured_media":17011,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3121],"tags":[3686,3692,3661,3691,3718,3716,3717,3715],"class_list":["post-17256","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","tag-azure-function","tag-azure-function-http-trigger","tag-azure-functions","tag-http-trigger","tag-http-trigger-cors","tag-http-trigger-query-string","tag-http-trigger-request-body","tag-http-trigger-route"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17256","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=17256"}],"version-history":[{"count":31,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17256\/revisions"}],"predecessor-version":[{"id":17292,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/17256\/revisions\/17292"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/17011"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=17256"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=17256"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=17256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}