asp.net webforms handle 404 notfound error in codebehind?












2















Just trying to detect if it's 404 error in application. For example user tries in url and IIS shows 404 not found.



I want to detect 404 error. Redirect to custom 404 page and pass message like "cound't find" dynamically from the codebehind.



Has anyone ever done that?










share|improve this question





























    2















    Just trying to detect if it's 404 error in application. For example user tries in url and IIS shows 404 not found.



    I want to detect 404 error. Redirect to custom 404 page and pass message like "cound't find" dynamically from the codebehind.



    Has anyone ever done that?










    share|improve this question



























      2












      2








      2








      Just trying to detect if it's 404 error in application. For example user tries in url and IIS shows 404 not found.



      I want to detect 404 error. Redirect to custom 404 page and pass message like "cound't find" dynamically from the codebehind.



      Has anyone ever done that?










      share|improve this question
















      Just trying to detect if it's 404 error in application. For example user tries in url and IIS shows 404 not found.



      I want to detect 404 error. Redirect to custom 404 page and pass message like "cound't find" dynamically from the codebehind.



      Has anyone ever done that?







      c# asp.net error-handling webforms web-config






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 13 '18 at 17:50







      Mert

















      asked Nov 13 '18 at 17:32









      MertMert

      226




      226
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Handle 404 using web.config custom errors, this is the correct way to handle this type of errors, and in NotFound.aspx page you can log the error.



          <configuration>
          <system.web>
          <customErrors mode="On" >
          <error statusCode="404" redirect="NotFound.aspx"/>
          </customErrors>
          </system.web>
          </configuration


          Noway to handle all 404 exceptions from code behind, because the generic handler of exception could be implemented in global.asax - (Application_Error method), this handler able to catch any error occurred on asp.net application layer and cannot handle 404 request because you are request something outside of asp.net.






          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%2f53286579%2fasp-net-webforms-handle-404-notfound-error-in-codebehind%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









            1














            Handle 404 using web.config custom errors, this is the correct way to handle this type of errors, and in NotFound.aspx page you can log the error.



            <configuration>
            <system.web>
            <customErrors mode="On" >
            <error statusCode="404" redirect="NotFound.aspx"/>
            </customErrors>
            </system.web>
            </configuration


            Noway to handle all 404 exceptions from code behind, because the generic handler of exception could be implemented in global.asax - (Application_Error method), this handler able to catch any error occurred on asp.net application layer and cannot handle 404 request because you are request something outside of asp.net.






            share|improve this answer






























              1














              Handle 404 using web.config custom errors, this is the correct way to handle this type of errors, and in NotFound.aspx page you can log the error.



              <configuration>
              <system.web>
              <customErrors mode="On" >
              <error statusCode="404" redirect="NotFound.aspx"/>
              </customErrors>
              </system.web>
              </configuration


              Noway to handle all 404 exceptions from code behind, because the generic handler of exception could be implemented in global.asax - (Application_Error method), this handler able to catch any error occurred on asp.net application layer and cannot handle 404 request because you are request something outside of asp.net.






              share|improve this answer




























                1












                1








                1







                Handle 404 using web.config custom errors, this is the correct way to handle this type of errors, and in NotFound.aspx page you can log the error.



                <configuration>
                <system.web>
                <customErrors mode="On" >
                <error statusCode="404" redirect="NotFound.aspx"/>
                </customErrors>
                </system.web>
                </configuration


                Noway to handle all 404 exceptions from code behind, because the generic handler of exception could be implemented in global.asax - (Application_Error method), this handler able to catch any error occurred on asp.net application layer and cannot handle 404 request because you are request something outside of asp.net.






                share|improve this answer















                Handle 404 using web.config custom errors, this is the correct way to handle this type of errors, and in NotFound.aspx page you can log the error.



                <configuration>
                <system.web>
                <customErrors mode="On" >
                <error statusCode="404" redirect="NotFound.aspx"/>
                </customErrors>
                </system.web>
                </configuration


                Noway to handle all 404 exceptions from code behind, because the generic handler of exception could be implemented in global.asax - (Application_Error method), this handler able to catch any error occurred on asp.net application layer and cannot handle 404 request because you are request something outside of asp.net.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 13 '18 at 18:32

























                answered Nov 13 '18 at 18:18









                Mohammad AlghanemMohammad Alghanem

                211114




                211114






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53286579%2fasp-net-webforms-handle-404-notfound-error-in-codebehind%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

                    Bressuire

                    Vorschmack

                    Quarantine