Why Laravel Resource Create and Edit operations are depicted using GET












1














I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?










share|improve this question


















  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40
















1














I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?










share|improve this question


















  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40














1












1








1


1





I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?










share|improve this question













I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?







laravel






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 at 7:23









Peter M

358315




358315








  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40














  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40








2




2




The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
– Kirk Beard
Nov 13 at 7:32




The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
– Kirk Beard
Nov 13 at 7:32












@KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
– Peter M
Nov 13 at 7:36






@KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
– Peter M
Nov 13 at 7:36






1




1




When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
– Kirk Beard
Nov 13 at 7:40




When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
– Kirk Beard
Nov 13 at 7:40












1 Answer
1






active

oldest

votes


















2














As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275822%2fwhy-laravel-resource-create-and-edit-operations-are-depicted-using-get%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






    share|improve this answer


























      2














      As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






      share|improve this answer
























        2












        2








        2






        As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






        share|improve this answer












        As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 at 7:33









        Kamal Paliwal

        730310




        730310






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275822%2fwhy-laravel-resource-create-and-edit-operations-are-depicted-using-get%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?